WIP Release infra stuff #485
Draft
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
snazy
requested review from
RussellSpitzer,
adutra,
ashvina,
collado-mike,
ebyhr,
eric-maynard,
flyrain,
jackye1995,
jbonofre,
takidau and
vvcephei
as code owners
snazy
force-pushed
the
releases-infra
branch
from
3197bf5 to
10132cf
Compare
Member
|
Thanks for that ! I will double check as I identified several issues during the first RC. |
Member
|
By the way, it would be great to sync: as said on the mailing list (in the release thread), I'm working on similar release script/check. I will sync with your PR. |
Member
Author
We did, I mentioned this in one of the calls, quite some time ago though ;) |
Member
@snazy you know I'm getting old, I didn't remember 😄 |
snazy
force-pushed
the
releases-infra
branch
13 times, most recently
from
e38a0e3 to
4d393f8
Compare
snazy
force-pushed
the
releases-infra
branch
21 times, most recently
from
b830904 to
5672e02
Compare
snazy
force-pushed
the
releases-infra
branch
2 times, most recently
from
d69c310 to
362a7af
Compare
Introduce a couple of shell scripts to automate the release process. Some docs are included under `releases/README.md`. Generally, releases at the ASF follow the following workflow: 1. Draft a release 2. Start a VOTE on the dev mailing list 3. If the VOTE fails, the release has failed - "go to step 1" 4. If the VOTE passes, publish the release The above process is, without release branches, reflected in the scripts: 1. `releases/bin/draft-release.sh --major <major-version-number> --minor <minor-version-number> --commit <Git-commit-ID>` 2. if the vote passes: `releases/bin/publish-release.sh --major <major-version-number> --minor <minor-version-number>` 3. if the vote fails, just run `draft-release.sh` again The change includes scripts to handle version branches, however, using those is not required for the two release scripts above. It's important to know that the scripts handle changes to the `version.txt` file and that a specific syntax for Git tags is expected, which is required to automatically use/generate RC and final versions, including the artifact publishing to Nexus.
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.
Introduce a couple of shell scripts to automate the release process. Some docs are included under
releases/README.md.Generally, releases at the ASF follow the following workflow:
The above process is, without release branches, reflected in the scripts:
releases/bin/draft-release.sh --major <major-version-number> --minor <minor-version-number> --commit <Git-commit-ID>releases/bin/publish-release.sh --major <major-version-number> --minor <minor-version-number>draft-release.shagainThe change includes scripts to handle version branches, however, using those is not required for the two release scripts above.
It's important to know that the scripts handle changes to the
version.txtfile and that a specific syntax for Git tags is expected, which is required to automatically use/generate RC and final versions, including the artifact publishing via Sonatype.