Creates a new issue template for releases #6972
Conversation
| - this is now public and notifies subscribed users | ||
| - publishes artefacts and version-specific docker tags | ||
| - [ ] Using the same git sha, create a new tag for the FULL RELEASE, example format 24.4.0 | ||
| - [ ] Using the FULL RELEASE tag, create a PRE-RELEASE in github to trigger the workflows |
There was a problem hiding this comment.
does this mean we get 2 pre-releases? one for the RC and one for the full release tag?
There was a problem hiding this comment.
this is copypasta from @siladu but i interpreted it as using pre-release is optional for RCs
There was a problem hiding this comment.
ok fair enough. DCO is broken tho
There was a problem hiding this comment.
This is the part I asked for feedback on.
This is also in flux due to #6963
Am currently testing out scenarios with this PR.
There was a problem hiding this comment.
Checklist has been updated in light of .#6963 (comment)
It will change again if and when we play #6994
| - [ ] Convert the DRAFT into a PRE-RELEASE | ||
| - this is now public and notifies subscribed users | ||
| - publishes artefacts and version-specific docker tags |
There was a problem hiding this comment.
I have removed this step from the WIP checklist as it would result in creating redundant 24.5.0-RC1 artefacts.
See #6963 (comment) for context.
Most of the time we will want to go straight from draft/burn-in -> full release, with pre-release being a necessary in-between step for now. That pre-release needs to use the full release tag e.g. 24.5.0 instead of 24.5.0-RC1.
| - this is now public and notifies subscribed users | ||
| - publishes artefacts and version-specific docker tags | ||
| - [ ] Using the same git sha, create a new tag for the FULL RELEASE, example format 24.4.0 | ||
| - [ ] Using the FULL RELEASE tag, create a PRE-RELEASE in github to trigger the workflows |
There was a problem hiding this comment.
| - [ ] Using the FULL RELEASE tag, create a PRE-RELEASE in github to trigger the workflows | |
| - [ ] Using the FULL RELEASE tag, create a PRE-RELEASE in github to trigger the workflows | |
| - this is now public and notifies subscribed users | |
| - publishes artefacts and version-specific docker tags |
Moving extra comments from the removed step above
No description provided.