Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Tag a release. This may either be a release candidate or a final release. For example:

    Code Block
    $ git tag -a 0.1.0-rc1 -m "Spin 1, Release Candidate 1"
    $ git tag -a 0.1.0 -m "Spin 1, Final Release"

    Remember to push the tag:

    Code Block
    $ git push --tags origin
  2. Create a new branch for the next spin

    Code Block
    $ git branch 0.2.0
    $ git push origin 0.2.0
  3. Change the default branch to the new branch in the Stash Daffodil Repo Settings.
  4. Update the automated build system to watch the new branch for changes.

From this point on, all new features are to be added to the new branch (e.g. 0.2.0) following the Development Workflow. All tests and bug fixes for the previous spin should be performed added on the previous that spins branch and immediately merged into the new branch by the person making the change:

Code Block
$ git checkout 0.1.0
# fix bug and/or add test verifying bug fix, commit and push changes
$ git checkout 0.2.0
$ git merge 0.1.0

Please see Step 19 of the Development Workflow for the correct merge/test/push workflow.