Skip to content

Branches and Releases

Damian Turczynski edited this page Oct 24, 2017 · 1 revision

I've been consolidating branches in a next release branch before merging into master to help version management a little bit. Haven't really worked out a better release management cycle than that for now.

If you want to PR, maybe ask first - if it's standalone and nothing else is going out in the same timeframe, the PR can probably target master. Otherwise, it might be merge-able into the next branch.

Current (WIP) Release Process

  • Create a new PR targeting the next branch (i.e. not master)
  • Release manager will merge into next, adding a link to the merged PR in the next PR description
  • Release manager will update the version and changelog in next
  • Release manager will build the release notes into the PR description
  • Release manager will merge next into master and tag the release, copying over the release notes
  • Release manager closes any associated Issues and leaves a comment with the release they were included in.

Release Notes

  • Should be included on the release/tag
  • Should have links to each PR that went into the release
  • Don't necessarily have to link to bugs (the PR will probably have links to them)