@@ -103,37 +103,28 @@ To push a release version
103103 assumes that there is no directory called ` tmp_gh-pages ` in the repository root. If it is
104104 present, remove it before running the script.
105105
106- 8 . Locally edit the root ` pom.xml ` so that ` mvn deploy ` works:
107- 1 . Under ` <modules> ` , comment out ` google-cloud-examples ` , ` google-cloud-testing ` , and
108- ` google-cloud-util ` .
109- 2 . Comment out the ` nexus-staging-maven-plugin ` plugin definition at the end of the file.
110-
111- ** Don't commit these changes.**
112-
113- 9 . Check that you are not trying to release a SNAPSHOT build (the artifacts versions do not have
106+ 8 . Check that you are not trying to release a SNAPSHOT build (the artifacts versions do not have
114107 "-SNAPSHOT" suffix) and then run ` mvn clean deploy -DskipTests=true --settings ~/.m2/settings.xml -P release `
115108 command. It will build and deploy artifacts to the staging repository.
116109
117110 ** Note:** you may need to specify the stagingProfileId with ` -DstagingProfileId=3187e4f20d328b `
118111 ** Note:** you may need to specify the GPG tty with ` GPG_TTY=$(tty) `
119112
120- 10 . Uncomment the ` nexus-staging-maven-plugin ` plugin definition from step 8; This plugin is
121- needed to release the artifacts. Run ` mvn nexus-staging:release ` to release the artifacts.
122-
123- 11 . Revert the local edits to your ` pom.xml ` performed a couple steps above by running ` git checkout pom.xml ` .
113+ 9 . Run ` mvn nexus-staging:release ` to release the artifacts. If you wish to abort the release, run
114+ ` mvn nexus-staging:drop ` .
124115
125- 12 . Run ` cd tmp_gh-pages && git push && cd .. ` to push the previously generated docs (step 7).
116+ 10 . Run ` cd tmp_gh-pages && git push && cd .. ` to push the previously generated docs (step 7).
126117
127- 13 . Run ` rm -rf tmp_gh-pages ` to remove the generated docs directory from your local machine.
118+ 11 . Run ` rm -rf tmp_gh-pages ` to remove the generated docs directory from your local machine.
128119
129- 14 . Run ` releasetool tag ` to publish a release on Github. It will list the last few merged PRs.
120+ 12 . Run ` releasetool tag ` to publish a release on Github. It will list the last few merged PRs.
130121 Select the newly merged release PR. Releasetool will create the GitHub release with notes
131122 extracted from the pull request and tag the new release.
132123
133- 15 . Run ` releasetool start ` to bump the next snapshot version. Select "snapshot" when prompted for
124+ 13 . Run ` releasetool start ` to bump the next snapshot version. Select "snapshot" when prompted for
134125 the release type. This will bump the artifact versions and create a pull request.
135126
136- 16 . Review and submit the PR.
127+ 14 . Review and submit the PR.
137128
138129Improvements
139130============
0 commit comments