Story #18249

Development process feedback

Added by Peter Amstutz 17 days ago. Updated 9 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

User had trouble because they cloned from github and got the development branch. Did not understand that 2.2-dev is actually a release branch.

Suggested changed

  • X.Y-dev should be called X.Y-release
  • make latest stable branch (e.g. "2.3-release") the default branch for github (add to release checklist)

History

#1 Updated by Peter Amstutz 17 days ago

  • Target version changed from 2021-10-13 sprint to 2021-10-27 sprint

#2 Updated by Peter Amstutz 17 days ago

  • Description updated (diff)

#3 Updated by Peter Amstutz 16 days ago

  • Description updated (diff)

#4 Updated by Peter Amstutz 15 days ago

  • Description updated (diff)

#5 Updated by Peter Amstutz 14 days ago

How about this:

  1. X.Y-dev is still actually a development branch for that release.
  2. When the release happens, we create a X.Y-release branch. This points to latest release in the X.Y series. The head of the branch should be the same as the tag for the latest release. This branch is only updated for actual releases.
  3. On each major release, go to github and set the "default branch" to the X.Y-release branch.

#6 Updated by Tom Clegg 14 days ago

It seems a bit weird to me to arrange our github setup to accommodate the (anti?)pattern of an install recipe that starts by cloning a git repo.

More ideas:
  • at https://doc.arvados.org/v2.2/install/salt-single-host.html, provide a snippet that does the exactly correct "git clone" command (the current language is "cloning the 2.2-dev branch from {url}" which makes it easy to forget the checkout step, and depending on familiarity with git might even be misinterpreted to mean "cloning {url} gives you the 2.2-dev branch")
  • in the provision.sh script, error out if being run from a git tree with a non-released version and the user isn't explicitly asking for a development version

#7 Updated by Peter Amstutz 9 days ago

  • Description updated (diff)

#8 Updated by Peter Amstutz 9 days ago

  • Description updated (diff)

#9 Updated by Peter Amstutz 9 days ago

  • Target version changed from 2021-10-27 sprint to 2021-11-10 sprint

Also available in: Atom PDF