Add release checklist issue template; Document some of our timelines around releases #1538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
because I'm tired of copy/paste
This should probably go elsewhere, but here is fine for now as a SCT-referenced doc/content.
richvdh
approved these changes
May 24, 2023
Comment on lines
+17
to
+22
| The SCT aims to have dates picked out by: | ||
|
|
||
| * Q1: January 10. | ||
| * Q2: May 1. | ||
| * Q3: August 1. | ||
| * Q4: October 15. |
There was a problem hiding this comment.
this is all very formal... Honestly I'd have thought "The SCT will normally announce a release date 2-3 weeks before the release" would be fine. Does anyone other than ourselves actually care exactly what release date is, to that degree?
There was a problem hiding this comment.
This doc is written for us, it just happens to be publicly accessible. We don't really have a good place to put process stuff like this, so I've stuck it in the release procedures. No one but us cares how to cut a release either :D
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale for the issue template: I'm tired of hitting copy/paste every 2 months 馃槢 If someone uses the issue template inappropriately, we'll treat it just like an improperly filed issue. Ideally we'd have a bot that creates this issue for us, but this is fine for now, I think.
As for the docs: many of the dates are pulled from thin air, but aren't too far off from what I already consider. I don't think the docs are in the right place here, but for sharing the knowledge as it exists this is probably fine for now.
Preview: https://pr1538--matrix-spec-previews.netlify.app