Update the RELEASING.md #324
Merged
Conversation
This file contains hidden or 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
Contributor
merks
commented
Jun 10, 2025
merks
commented
- The is copied to create a new issue but a number of versions could be made more current.
Contributor
Author
|
I've been working on a simple class that can be used to update all the necessary EPP things and does so with quite selective patterns so that we don't accidentally end up with bad changes. See below. I wanted to try this out to for prepare for M1. It would be nice to have more confidence that one can simply specify the versions in one place has have it properly applied... Note that I have already started the 2025-09 staging.
|
jonahgraham
approved these changes
Jun 11, 2025
RELEASING.md
Outdated
|
|
||
| - [ ] **24 Hours before Final release** Make sure files are in final location to allow downloads to mirror | ||
| - [ ] Tag the release, e.g. with 2020-03_R. Example command line: `git tag --annotate 2020-03_R -m"2020-03 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b` | ||
| - [ ] Tag the release, e.g. with 2025-09_R. Example command line: `git tag --annotate 2050-09_R -m"2025-09 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b` |
Contributor
There was a problem hiding this comment.
I wasn't sure if this was an intentional mistake to ensure whoever copied-pasted it couldn't create a bad tag.
Suggested change
| - [ ] Tag the release, e.g. with 2025-09_R. Example command line: `git tag --annotate 2050-09_R -m"2025-09 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b` | |
| - [ ] Tag the release, e.g. with 2025-09_R. Example command line: `git tag --annotate 2025-09_R -m"2025-09 Release" 1b7a1c1af156e3ac57768b87be258cd22b49456b` |
Contributor
There was a problem hiding this comment.
PS if intentional, the thing to make "fake" is probably the sha1 so that the git tag will fail
- The is copied to create a new issue but a number of versions could be made more current.
merks
force-pushed
the
pr-update-releasing.md
branch
from
a8bdb5b to
116a716
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.