This is an automated email from the ASF dual-hosted git repository. toulmean pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-tuweni.git
commit fd9f67f3a6e5df36400fdcc027e0f7316ccf24e8 Author: Antoine Toulme <[email protected]> AuthorDate: Sat Nov 30 17:56:15 2019 -0800 Simplify release instructions --- RELEASE.md | 100 +++++++++++-------------------------------------------------- 1 file changed, 17 insertions(+), 83 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index cfc6d32..dc41b7c 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -28,91 +28,33 @@ For patch releases, use the existing release branch. ## Prepare the release -Change the README file to update version numbers to the new release. Make a commit ($commitId) to the release branch and push. -TODO : point to commit example - Change the version number in the master branch in a commit and push. -TODO : point to commit example + +Example: https://github.com/apache/incubator-tuweni/commit/0330d134f579034b9d943870ea31316899632a11 ## Running the release -### Build the artifacts +In your release branch: -Set up the version strategy: ``` export BUILD_RELEASE=true -``` - -Build the artifacts -``` -./gradlew build -``` - -Check the sha512 signatures match -``` -shasum -a 512 dist/build/distributions/tuweni-bin-${RELEASE VERSION}.tgz -shasum -a 512 dist/build/distributions/tuweni-bin-${RELEASE VERSION}.zip -shasum -a 512 dist/build/distributions/tuweni-src-${RELEASE VERSION}.tgz -shasum -a 512 dist/build/distributions/tuweni-src-${RELEASE VERSION}.zip -shasum -a 512 dist/build/distributions/tuweni-gossip-${RELEASE VERSION}.tgz -shasum -a 512 dist/build/distributions/tuweni-gossip-${RELEASE VERSION}.zip -shasum -a 512 dist/build/distributions/tuweni-relayer-${RELEASE VERSION}.tgz -shasum -a 512 dist/build/distributions/tuweni-relayer-${RELEASE VERSION}.zip -``` - -Sign and publish -``` export ENABLE_SIGNING=true -./gradlew publish -``` - -This checks the code, the licenses, runs all the tests and creates all the artifacts (binaries, sources, javadoc). - -This also publishes the artifacts to repository.apache.org in a staging repository. - -### Push the distribution to dist.apache.org staging area - -Delete the folder if necessary: -``` -svn delete https://dist.apache.org/repos/dist/dev/incubator/tuweni/${RELEASE VERSION} -m "Deleting release candidate ${RELEASE_VERSION}" -``` - -Create the folder: -``` -svn mkdir -m "Add new Tuweni folder for release ${RELEASE VERSION}" https://dist.apache.org/repos/dist/dev/incubator/tuweni/${RELEASE VERSION} -``` - -Check out the folder locally: -``` -svn checkout https://dist.apache.org/repos/dist/dev/incubator/tuweni/${RELEASE VERSION} _staged +./gradlew stage ``` -Copy the distribution artifacts to it - make sure to change the name to ${RELEASE VERSION}-incubating: - -``` -cp dist/build/distributions/tuweni-${RELEASE VERSION}.zip _staged/tuweni-${RELEASE VERSION}-incubating.zip -cp dist/build/distributions/tuweni-${RELEASE VERSION}.tgz _staged/tuweni-${RELEASE VERSION}-incubating.tgz -``` +### Close the staged repository for the release -Commit the changes: -``` -cd _staged -svn add tuweni-* -svn ci -m "Add Apache Tuweni ${RELEASE VERSION} release candidate" -``` +Go to repository.apache.org and find the open repository that was created during the upload. -### Tag the git repository +Click "Close" in the workflow buttons at the top. -``` -git tag -m "Release ${RELEASE VERSION}" v${RELEASE VERSION} -git push origin ${RELEASE BRANCH} --tags -``` +### Make release notes -### Close the staged repository for the release +Go to github.com, click tags and find your release. -Go to repository.apache.org and find the open repository that was created during the upload. +Edit the tag and add release notes. -Click "Close" in the workflow buttons at the top. +Make sure to mark the release as "pre-release". ### Open a thread for a vote @@ -142,6 +84,7 @@ After the time of the vote has elapsed, close the vote thread with a recap showi ## Incubator general list The next step is to email the general incubator list. If 3 IPMC votes were collected in the first vote, this is a notification. + If less than 3 votes were collected, this email is a new vote asking for more IPMC +1s. ## Close the vote @@ -156,15 +99,6 @@ Move the files from `https://dist.apache.org/repos/dist/dev/incubator/tuweni/${R svn move -m "Move Apache Tuweni ${RELEASE VERSION} to releases" https://dist.apache.org/repos/dist/dev/incubator/tuweni/${RELEASE VERSION} https://dist.apache.org/repos/dist/release/incubator/tuweni/${RELEASE VERSION} ``` -Update the website: - -Go to the repository here and perform this change: - -https://github.com/apache/incubator-tuweni-website/commit/77066736df2997991e3a1954f41ced1c7a52999d - -Test the downloads page (wait 24h for mirrors to update): - - ### Release the artifacts to maven central Go to repository.apache.org to the closed repository you closed during the RC process. @@ -173,17 +107,17 @@ Click on it and press the release workflow button at the top. ### Publish the site +Go to the repository here and perform this change: + +https://github.com/apache/incubator-tuweni-website/commit/77066736df2997991e3a1954f41ced1c7a52999d + Go to builds.apache.org, and run this build: https://builds.apache.org/job/Apache%20Tuweni/job/website/ It takes an hour for the changes to be pushed out. -### Make release notes - -Go to github.com, click tags and find your release. - -Edit the tag and add release notes. +Test the downloads page (wait 24h for mirrors to update). ### Send an [ANNOUNCE] email --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
