Revision: 1220
Author: heue...@gmail.com
Date: Tue Nov 26 21:17:41 2013 UTC
Log: replace manual release steps with maven release plugin
http://code.google.com/p/piccolo2d/source/detail?r=1220
Modified:
/wiki/ReleaseChecklist.wiki
=======================================
--- /wiki/ReleaseChecklist.wiki Tue Nov 26 17:47:33 2013 UTC
+++ /wiki/ReleaseChecklist.wiki Tue Nov 26 21:17:41 2013 UTC
@@ -7,18 +7,8 @@
# Verify that no Fixed issues exist with the current release milestone
* (All closed issues should be in Duplicate, WontFix, or Verified
status
*
[http://code.google.com/p/piccolo2d/issues/list?can=1&q=Milestone:1.3.2%20status=Fixed&sort=status&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Toolkit%20Component%20Summary
Milestone:1.3.2,status=Fixed]
-===Release Candidates===
+===Verify build===
* For each of {beta, rc1, rc2, ...} release candidates:
- # Clean checkout of trunk (or primary branch) from subversion:
-{{{
-$ svn checkout https://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk
piccolo2d.java-trunk
-$ cd piccolo2d.java-trunk
-}}}
- # Update version in all pom.xml files to
{$version}-${release-candidate}
- * `*`/pom.xml:
-{{{
- <version>1.3.2-rc1</version>
-}}}
# Verify that working directory builds and all tests pass on all
platforms:
{{{
$ mvn install
@@ -29,12 +19,11 @@
$ mvn assembly:assembly
$ java -jar target/piccolo2d-examples-1.3.2-rc1-jar-with-dependencies.jar
}}}
- * _Note: The maven assembly plugin is deprecating (see
[http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html
here]) all goals (including assembly:assembly) except for assembly:single.
However, mvn assembly:single currently fails to correctly build the
assembly; likely having something to do with
[http://jira.codehaus.org/browse/MASSEMBLY-94 this Maven ticket]. The
workaround is to use run the clean and package phase at the same time as
assembly:single (i.e., {{{mvn clean package assembly:single"}}}) or use mvn
assembly:assembly so long as it is still available._
# Verify that the SWT examples run with the specified jdk version on
all platforms
{{{
$ cd ../swt-examples
$ mvn assembly:assembly
-$ java -jar
target/piccolo2d-swt-examples-1.3.2-beta-jar-with-dependencies.jar
+$ java -jar
target/piccolo2d-swt-examples-1.3.2-rc1-jar-with-dependencies.jar
}}}
# Verify that {{{clirr}}} report shows no ERRORs where binary
compatibility is required
* For example, for minor release version 1.3.2, core must be binary
compatible with the latest minor release version, 1.3.
@@ -45,65 +34,18 @@
# Class file format of all jar files matches the minimum required JDK
version, currently 1.4
* _Note: I did this by unzipping the built jars and using
{{{javap}}}; there may be a better way to do this verification, or perhaps
we should author a script._
# Update release notes and readme as necessary
- # Commit release candidate changes to trunk
-{{{
-$ svn commit -m "updating version to 1.3.2-rc1" .
-}}}
- # Create release tag in subversion
-{{{
-$ svn cp -m "creating 1.3.2-rc1 release tag"
https://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk
https://piccolo2d.googlecode.com/svn/piccolo2d.java/tags/release-1.3.1-rc1
-}}}
- # Create binary, source, and javadoc release artifacts
- * To create binary zip and binary tar.gz files, update the VERSION
shell variable and call
-{{{
-$ ./create-bin.sh
-}}}
- * To create source zip and source tar.gz files, update the VERSION
shell variable and call
-{{{
-$ ./create-src.sh
-}}}
- * These scripts are currently attached to Issue 146 and will
probably live in svn shortly.
- # Create new downloads on Google Code
- * Visit http://code.google.com/p/piccolo2d/downloads/list
- * Click [http://code.google.com/p/piccolo2d/downloads/entry New
download] link and upload binary zip, binary tar.gz, source zip, and source
tar.gz files. Refer to previous uploads for what the metadata should look
like.
- * Deprecate earlier failed release candidate version downloads, if
any.
- # Consider syncing release candidates to Maven Repository (follow same
process as for a release, below) to encourage community usage of release
candidates.
-===After final release tag:===
+===Maven Release Plugin===
- * Create release branch in subversion
-{{{
-$ svn cp -m "creating 1.3.2 release branch"
https://piccolo2d.googlecode.com/svn/piccolo2d.java/trunk
https://piccolo2d.googlecode.com/svn/piccolo2d.java/branches/release-1.3.2
-}}}
- * Create bundle(s) for upload to maven central repository
- * First, if you don't already have one, you'll need a PGP code signing
key available from the MIT keyserver, see:
[http://code.google.com/p/piccolo2d/wiki/OpenPGPConfiguration
OpenPGPConfiguration]. You'll also need to sign up for an account with
[https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-2.Signup
Sonatype] in order to stage artifacts that will be synced to Maven Central.
- * The
[https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
Sonatype OSS Guide] describes the full process of syncing open-source
artifacts to the Maven central repository.
- * See the section on
[https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7b.StageExistingArtifacts
staging existing artifacts]. This is the easiest way to control the
process; we've been wary to trust {{{mvn release}}} to perform the pom
modifications and svn operations.
- * If building and staging the artifacts by hand, for each module
use
-{{{
-mvn source:jar javadoc:jar gpg:sign
-}}}
- which will produced signed versions of source, javadoc and
binaries in the target directory. Example:
{{{
-$ cd core
-$ mvn source:jar javadoc:jar gpg:sign
-$ cd target
-$ jar -cvf bundle.jar *.pom *.jar *.asc
+$ mvn -DautoVersionSubmodules=true release:prepare
}}}
- * Then manually stage/upload the bundle.jar through Nexus
Sonatype UI.
- * More about signing artifacts with Maven GPG can be found
[https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
here].
- * After releasing, update version in pom.xml files on svn trunk to
${next-version}-SNAPSHOT
-parent/pom.xml:
{{{
- <version>1.4-SNAPSHOT</version>
+$ mvn release:perform
}}}
-and commit
-{{{
-$ svn commit -m "updating version to 1.4-SNAPSHOT" parent/pom.xml
-}}}
===Update the website, wiki, and announce the release===
--
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
---
You received this message because you are subscribed to the Google Groups "Piccolo2D Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to piccolo2d-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
