[Release procedures] Document migration of issues/PRs milestones

[joewiz]

What is the problem

The current release documentation https://github.com/eXist-db/exist/blob/develop/exist-versioning-release.md doesn't instruct us how to migrate open issues and PRs to the next release milestones. As we know, it's possible to mess this procedure up, so to prevent problems and make it possible for others to help with this task, we should add directions to the exist-versioning-release.md document (or elsewhere) for:

1. creating new milestones and assigning due dates to release day + 2 months
2. migrating open issues/PRs to the appropriate new milestone
3. closing old milestones

Does anyone have something like this written up? If not, can someone who knows the procedure write it up?

The milestones page: https://github.com/eXist-db/exist/milestones

[duncdrum]

Let's also add a note about the need to simultaneously push a tag and make a release on GH, so that the automated docker builds don't get tagged with the wrong version. This worked well for 4.5.0 with 4.6.0 there were 20h between pushing the tag and creating the GH release.

[adamretter]

@duncdrum As we cannot control the time between pushing the tag and creating the GH release, I think the onus to become more resilient to clock skew there has to be on the automated Docker build side.

[duncdrum]

@adamretter we have full control over the GitHub release creation. You can create it whenever you want, and modify it to e.g. update changelog, and attachments as necessary at a later point in time. We can do this manually, or automated like in the documentation app, or via Travis, or …

This flimsiness is direct consequence of our design decision to not include the docker files here in the main repo, but maintain a separate repo instead. So the onus is very much here to clarify if a pushed tag actually signifies a release or not.

[adamretter]

@joewiz As requested, I just updated the milestones and wrote some documentation for migrating milestones... would you be able to clean up my text and add it to the relevant place?

Docs

For example, assuming the release was 4.6.1 i.e. a Hotfix release, we can migrate any remaining open issues from eXist-4.6.1 milestone to a new eXist-4.6.2 milestone:

1. Visit the https://github.com/eXist-db/exist/milestones page
2. Create a new hotfix milestone eXist-4.6.2, set the due date to the date of the eXist-4.6.1 tag plus two months (don't worry about the number of days exactly, just bump the month by 2), set the description to "Next Hotfix Release"
3. Click the eXist-4.6.1 milestone
4. Select all the open issues, click milestone drop-down, and then click eXist-4.6.2
5. Click Edit milestone and then click Close milestone

If the release was a Minor release, you also need to do a very similar process for a new Minor milestone, however the description should be, "Next Minor Release".

[joewiz]

@adamretter Thank you, this looks good. Will do. I'll also update the homebrew directions for rc.

[line-o]

I assume that this issue was resolved and therefore propose to close it.