Permalink
Browse files

revised steps

  • Loading branch information...
inder123 committed Sep 20, 2017
1 parent 4c3e471 commit fbaa708b41ad382bb1da55821986a7a78012643d
Showing with 3 additions and 3 deletions.
  1. +3 −3 ReleaseProcess.md
View
@@ -3,10 +3,10 @@
The following is a step-by-step procedure for releasing a new version of Google-Gson.
1. Go through all open bugs and identify which will be fixed in this release. Mark all others with an appropriate release tag. Identify duplicates, and close the bugs that will never be fixed. Fix all bugs for the release, and mark them fixed.
1. Edit [`pom.xml`](pom.xml) and update the versions listed for Export-Package to the target version. Also add any new Java packages that have been introduced in Gson.
1. (obsolete step) Edit [`pom.xml`](pom.xml) and update the versions listed for Export-Package to the target version. Also add any new Java packages that have been introduced in Gson.
1. Ensure all changelists are code-reviewed and have +1
1. Ensure that your `~/.m2/settings.xml` is configured properly (see steps below)
1. `cd gson`; ensure there are no open files and all changes are committed.
1. (obsolete step) Ensure that your `~/.m2/settings.xml` is configured properly (see steps below)
1. `cd gson` to the parent directory; ensure there are no open files and all changes are committed.
1. Run `mvn release:clean`
1. Do a dry run: `mvn release:prepare -DdryRun=true`
1. Start the release: `mvn release:prepare`

0 comments on commit fbaa708

Please sign in to comment.