snazy commented on PR #485:
URL: https://github.com/apache/polaris/pull/485#issuecomment-2504635054
Some examples that work now. When you try the following commands without the
`--dry-run` flag, make sure to let your local `versioned-docs` branch use a
_different_ upstream repository than `apache/polaris`.
* `releases/bin/draft-release.sh --major 0 --minor 1`
* Using the version `0.1.0-incubating-rc1`
* Creates release notes from relevant Git commits
* When run in GH actions: Publish to the maven artifacts to Apache's
Sonatype (published to the local maven repo otherwise) & generates source
tarball
* Uploads the source tarball to the ASF SVN (only when run in GH actions,
otherwise to a _local_ "replacement" SVN repo)
* Creates the `apache-polaris-0.1.0-rc1` tag using a new commit from the
"base commit" that has the changes purely for that release (release notes,
staging repo information).
* Pushes the changes to the upstream _git_ repository
* Prints "VOTE" vote email subject and body proposal
* Pushes the Git tag
* Calling `releases/bin/draft-release.sh --major 0 --minor 1` (same
major/minor version) again works similarly, but
* Uses the version `0.1.0-incubating-rc2`
* Creates the `apache-polaris-0.1.0-rc2` tag,
* Replaces the RC1 source tarball with the one for RC2
* `releases/bin/publish-release.sh --major 0 --minor 1`
* Adds the `apache-polairs-0.1.0` tag (to the same commit as the latest RC
tag `apache-polaris-0.1.0-rc2`)
* Adds the `apache-polaris-0.1.0-incubating` source tarball to the
releases-SVN (local SVN, if not run via GH actions)
* Removes all source tarballs for 0.1.0 from the dev-SVN
* When run in GH actions: release the staging Sonatype repository
* Pushes the new Git tag
* Prints "ANNOUNCE" email subject and body proposa
* Generates (copies) + adds the 0.1.0 version to the versioned-docs branch
* Running `releases/bin/publish-release.sh --major 0 --minor 1` again
results in an error message (no RC for the "latest" 0.1.x)
* Calling `releases/bin/draft-release.sh --major 0 --minor 1`
* Would work like above, but for 0.1.1 (the **next** patch release)
This change is not yet ready, but it looks very promising.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
