[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Michael Dick (Apr 27, 2007). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. These instructions are specific to the incubating status of OpenJPA. Once OpenJPA is elevated out of incubation, these instructions will need to be updated. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: JDK 1.5 ssh 2 maven 2 gpg Tasks that need to be performed for each release In the examples below, it is assumed that the current committed version of OpenJPA is 0.9.6-incubating-SNAPSHOT, and the version of the official release will be 0.9.6-incubating 1 Make sure the One time setup steps have been performed 2 If releasing from the trunk, first make a branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more distruptive advances in the trunk from potentially causing problems with the release. A branch can be made by running: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/trunk https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-incubating 3 Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: perl -pi -e 's;version0.9.6-incubating-SNAPSHOT/version;version0.9.6-incubating/version;g' pom.xml */pom.xml 4 Commit the POM changes svn commit -m "Updated to version 0.9.6-incubating" 5 Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): mvn clean install -Pdocbook-profile,sign-release This operation will also sign the release files with the gpg utility using the username@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: [EMAIL PROTECTED] 6 Verify the signatures: gpg --multifile --verify openjpa-project/target/assembly/*.asc 7 Now actually build the javadocs and perform the deploy upload: mvn verify deploy -Pjavadoc-profile,sign-release 8 Tag the branch with the release number: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/branches/0.9.6-incubating https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating 9 Update the pom.xml files to the subsequent version with the SNAPSHOT suffix: perl -pi -e "s;version0.9.6-incubating/version;version0.9.7-incubating-SNAPSHOT/version;g" pom.xml */pom.xml 10 Commit the POM changes svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT" 11 Start a vote for the release on the [EMAIL PROTECTED] mailing list. Votes made by committers and members of the OpenJPA project are considered binding for this vote. For an example of the mail, see this archived vote 12 If the vote is successful after 3 days tally the votes in an email to [EMAIL PROTECTED] then mail [EMAIL PROTECTED] starting a vote for authorization to release. For this vote only the members of the IPMC are considered binding. A list of the IPMC members can be found here. 13 Once that vote is successful, update the http://cwiki.apache.org/openjpa/downloads.html page with information about the download 14 The documentation links at http://cwiki.apache.org/openjpa/documentation.html also needs to be updated. You can do this by checking out a copy of the OpenJPA static site documents into a scratch directory, unpacking the OpenJPA binary into the docs section, adding the new docs, and then committing and updating the docs on the server-side: mkdir /tmp/openjpa-docs/ cd /tmp/openjpa-docs/ jar xvf OPENJPA_DIR/openjpa-project-0.9.6-incubating-binary.zip mkdir /tmp/openjpa-site/ cd /tmp/openjpa-site/ svn co https://svn.apache.org/repos/asf/incubator/openjpa/site/docs cd docs/docs/ mv /tmp/openjpa-docs/openjpa-0.9.6-incubating/docs/ openjpa-0.9.6-incubating rm latest ln -s openjpa-0.9.6-incubating latest svn add openjpa-0.9.6-incubating svn commit -m "Added documentation for openjpa-0.9.6-incubating release" . ssh people.apache.org svn co http://svn.apache.org/repos/asf/incubator/openjpa/site/docs /www/incubator.apache.org/openjpa The static site will take a little while to synchronize, but
[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Marc Prudhommeaux (Nov 10, 2006). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: JDK 1.5 ssh 2 maven 2 gpg Tasks that need to be performed for each release In the examples below, it is assumed that the current committed version of OpenJPA is 0.9.6-incubating-SNAPSHOT, and the version of the official release will be 0.9.6-incubating 1 Make sure the One time setup steps have been performed 2 Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: perl -pi -e 's;version0.9.6-incubating-SNAPSHOT/version;version0.9.6-incubating/version;g' pom.xml */pom.xml 3 Commit the POM changes svn commit -m "Updated to version 0.9.6-incubating" 4 Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): mvn clean install -Pdocbook-profile,sign-release This operation will also sign the release files with the gpg utility using the username@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: [EMAIL PROTECTED] 5 Verify the signatures: gpg --multifile --verify openjpa-project/target/assembly/*.asc 6 Now actually build the javadocs and perform the deploy upload: mvn verify deploy -Pjavadoc-profile,sign-release 7 Tag the view with the release number: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/trunk https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating 8 Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix: perl -pi -e "s;version0.9.6-incubating/version;version0.9.7-incubating-SNAPSHOT/version;g" pom.xml */pom.xml 9 Commit the POM changes svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT" 10 Start a vote for the release on the open-jpa-dev@incubator.apache.org mailing list. For an example of the mail, see this archived vote One time setup These setup steps only need to be performed on a particular machine once. Developers using Linux workstations can skip over the references to PuTTY and Cygwin Create and install a SSH key 1 Install PuTTY 2 Use PuttyGen to create a SSH key (see Putty help for details) 3 Use PuTTY to ssh to people.apache.org 4 Create a ~/.ssh folder 5 pscp your SSH public key to ~/authorized_keys 6 ssh to p.a.o 7 Create a ~\.ssh folder and move authorized_keys there 8 Configure putty to use your private key and save the session Create a PGP key 1 Install cgywin, including utils/gpg 2 Generate a key with $ gpg --gen-key 3 Backup your cygwin home directory to another media 4 Add your key to https://svn.apache.org/repos/asf/incubator/openjpa/site/docs/KEYS Update Maven settings for our servers 1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows) settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" servers server idpeople.apache.org/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server /servers /settings Expose a copy of known hosts to Maven 1 From cygwin, ssh to people.apache.org, save the public key if prompted, and exit cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows) 2 From cygwin (not Windows) create another .ssh folder at 3 Copy the known_hosts file to the new .ssh folder Resources Apache Guide To Release Management During Incubation Signing Releases Wendy's notes on Release Signing Apache Mirroring Guidelines Struts Release Instructions (upon which these instructions are based) Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request Unsubscribe or edit your notifications preferences
[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Marc Prudhommeaux (Nov 10, 2006). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: JDK 1.5 ssh 2 maven 2 gpg Tasks that need to be performed for each release In the examples below, it is assumed that the current committed version of OpenJPA is 0.9.6-incubating-SNAPSHOT, and the version of the official release will be 0.9.6-incubating 1 Make sure the One time setup steps have been performed 2 Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: perl -pi -e 's;version0.9.6-incubating-SNAPSHOT/version;version0.9.6-incubating/version;g' pom.xml */pom.xml 3 Commit the POM changes svn commit -m "Updated to version 0.9.6-incubating" 4 Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): mvn clean install -Pdocbook-profile,sign-release This operation will also sign the release files with the gpg utility using the username@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: [EMAIL PROTECTED] 5 Verify the signatures: gpg --multifile --verify openjpa-project/target/assembly/*.asc 6 Now actually build the javadocs and perform the deploy upload: mvn verify deploy -Pjavadoc-profile,sign-release 7 Tag the view with the release number: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/trunk https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating 8 Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix: perl -pi -e "s;version0.9.6-incubating/version;version0.9.7-incubating-SNAPSHOT/version;g" pom.xml */pom.xml 9 Commit the POM changes svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT" 10 Start a vote for the release on the open-jpa-dev@incubator.apache.org mailing list. For an example of the mail, see this archived vote 11 If the vote is successful after 3 days, mail general@incubator.apache.org starting a vote for authorization to release 12 Once that vote is successful, update the http://cwiki.apache.org/openjpa/downloads.html page with information about the download One time setup These setup steps only need to be performed on a particular machine once. Developers using Linux workstations can skip over the references to PuTTY and Cygwin Create and install a SSH key 1 Install PuTTY 2 Use PuttyGen to create a SSH key (see Putty help for details) 3 Use PuTTY to ssh to people.apache.org 4 Create a ~/.ssh folder 5 pscp your SSH public key to ~/authorized_keys 6 ssh to p.a.o 7 Create a ~\.ssh folder and move authorized_keys there 8 Configure putty to use your private key and save the session Create a PGP key 1 Install cgywin, including utils/gpg 2 Generate a key with $ gpg --gen-key 3 Backup your cygwin home directory to another media 4 Add your key to https://svn.apache.org/repos/asf/incubator/openjpa/site/docs/KEYS Update Maven settings for our servers 1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows) settings.xml settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" servers server idpeople.apache.org/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server /servers /settings Expose a copy of known hosts to Maven 1 From cygwin, ssh to people.apache.org, save the public key if prompted, and exit cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows) 2 From cygwin (not Windows) create another .ssh folder at 3 Copy the known_hosts file to the new .ssh folder Resources Apache Guide To Release Management During Incubation Signing Releases Wendy's notes on Release Signing Apache Mirroring Guidelines Struts Release Instructions (upon which these
[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Marc Prudhommeaux (Nov 10, 2006). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. These instructions are specific to the incubating status of OpenJPA. Once OpenJPA is elevated out of incubation, these instructions will need to be updated. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: JDK 1.5 ssh 2 maven 2 gpg Tasks that need to be performed for each release In the examples below, it is assumed that the current committed version of OpenJPA is 0.9.6-incubating-SNAPSHOT, and the version of the official release will be 0.9.6-incubating 1 Make sure the One time setup steps have been performed 2 Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: perl -pi -e 's;version0.9.6-incubating-SNAPSHOT/version;version0.9.6-incubating/version;g' pom.xml */pom.xml 3 Commit the POM changes svn commit -m "Updated to version 0.9.6-incubating" 4 Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): mvn clean install -Pdocbook-profile,sign-release This operation will also sign the release files with the gpg utility using the username@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: [EMAIL PROTECTED] 5 Verify the signatures: gpg --multifile --verify openjpa-project/target/assembly/*.asc 6 Now actually build the javadocs and perform the deploy upload: mvn verify deploy -Pjavadoc-profile,sign-release 7 Tag the view with the release number: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/trunk https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating 8 Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix: perl -pi -e "s;version0.9.6-incubating/version;version0.9.7-incubating-SNAPSHOT/version;g" pom.xml */pom.xml 9 Commit the POM changes svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT" 10 Start a vote for the release on the open-jpa-dev@incubator.apache.org mailing list. For an example of the mail, see this archived vote 11 If the vote is successful after 3 days, mail general@incubator.apache.org starting a vote for authorization to release 12 Once that vote is successful, update the http://cwiki.apache.org/openjpa/downloads.html page with information about the download One time setup These setup steps only need to be performed on a particular machine once. Developers using Linux workstations can skip over the references to PuTTY and Cygwin Create and install a SSH key 1 Install PuTTY 2 Use PuttyGen to create a SSH key (see Putty help for details) 3 Use PuTTY to ssh to people.apache.org 4 Create a ~/.ssh folder 5 pscp your SSH public key to ~/authorized_keys 6 ssh to p.a.o 7 Create a ~\.ssh folder and move authorized_keys there 8 Configure putty to use your private key and save the session Create a PGP key 1 Install cgywin, including utils/gpg 2 Generate a key with $ gpg --gen-key 3 Backup your cygwin home directory to another media 4 Add your key to https://svn.apache.org/repos/asf/incubator/openjpa/site/docs/KEYS Update Maven settings for our servers 1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows) settings.xml settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" servers server idpeople.apache.org/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server /servers /settings Expose a copy of known hosts to Maven 1 From cygwin, ssh to people.apache.org, save the public key if prompted, and exit cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows) 2 From cygwin (not Windows) create another .ssh folder at 3 Copy the known_hosts file to the new .ssh folder Example shell script to perform the
[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Marc Prudhommeaux (Nov 09, 2006). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: JDK 1.5 ssh 2 maven 2 gpg Tasks that need to be performed for each release In the examples below, it is assumed that the current committed version of OpenJPA is 0.9.6-incubating-SNAPSHOT, and the version of the official release will be 0.9.6-incubating 1 Make sure the One time setup steps have been performed 2 Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: perl -pi -e 's;version0.9.6-incubating-SNAPSHOT/version;version0.9.6-incubating/version;g' pom.xml */pom.xml 3 Commit the POM changes svn commit -m "Updated to version 0.9.6-incubating" 4 Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): mvn clean install -Pdocbook-profile,sign-release This operation will also sign the release files with the gpg utility using the username@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: [EMAIL PROTECTED] 5 Verify the signatures: gpg --multifile --verify openjpa-project/target/assembly/*.asc 6 Now actually build the javadocs and perform the deploy upload: mvn verify deploy -Pjavadoc-profile,sign-release 7 Tag the view with the release number: svn copy -m "OpenJPA Release 0.9.6-incubating" https://svn.apache.org/repos/asf/incubator/openjpa/trunk https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating 8 Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix: perl -pi -e "s;version0.9.6-incubating/version;version0.9.7-incubating-SNAPSHOT/version;g" pom.xml */pom.xml 9 Commit the POM changes svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT" One time setup These setup steps only need to be performed on a particular machine once. Developers using Linux workstations can skip over the references to PuTTY and Cygwin Create and install a SSH key 1 Install PuTTY 2 Use PuttyGen to create a SSH key (see Putty help for details) 3 Use PuTTY to ssh to people.apache.org 4 Create a ~/.ssh folder 5 pscp your SSH public key to ~/authorized_keys 6 ssh to p.a.o 7 Create a ~\.ssh folder and move authorized_keys there 8 Configure putty to use your private key and save the session Create a PGP key 1 Install cgywin, including utils/gpg 2 Generate a key with $ gpg --gen-key 3 Backup your cygwin home directory to another media 4 Add your key to https://svn.apache.org/repos/asf/incubator/openjpa/site/docs/KEYS Update Maven settings for our servers 1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows) settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" servers server idpeople.apache.org/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server /servers /settings Expose a copy of known hosts to Maven 1 From cygwin, ssh to people.apache.org, save the public key if prompted, and exit cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows) 2 From cygwin (not Windows) create another .ssh folder at 3 Copy the known_hosts file to the new .ssh folder Resources Apache Guide To Release Management During Incubation Signing Releases Wendy's notes on Release Signing Apache Mirroring Guidelines Struts Release Instructions (upon which these instructions are based) Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request Unsubscribe or edit your notifications preferences
[CONF] OpenJPA: Releasing OpenJPA (page edited)
Page Edited : openjpa : Releasing OpenJPA Releasing OpenJPA has been edited by Marc Prudhommeaux (Nov 08, 2006). (View changes) Content: Making an OpenJPA Release These instructions guide through the steps of making an official OpenJPA release. Prerequisites You should have read the Apache Guide To Release Management During Incubation You must have shell access to people.apache.org You must have the following utilities installed on your local machine and available in your path: ssh 2 maven 2 gpg One time setup Developers using Linux workstations can skip over the references to PuTTY and Cygwin Create and install a SSH key 1 Install PuTTY 2 Use PuttyGen to create a SSH key (see Putty help for details) 3 Use PuTTY to ssh to people.apache.org 4 Create a ~/.ssh folder 5 pscp your SSH public key to ~/authorized_keys 6 ssh to p.a.o 7 Create a ~\.ssh folder and move authorized_keys there 8 Configure putty to use your private key and save the session Create a PGP key 1 Install cgywin, including utils/gpg 2 Generate a key with $ gpg --gen-key 3 Backup your cygwin home directory to another media 4 Add your key to https://svn.apache.org/repos/asf/incubator/openjpa/site/docs/KEYS Update Maven settings for our servers 1 Create a settings.xml under .m2 (in your Document and Settings folder) settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" !-- Uncomment this when the 'central' repo on ibiblio is down See: http://maven.apache.org/guides/mini/guide-mirror-settings.html -- !-- mirrors mirror idggi-project.org/id urlhttp://ftp.ggi-project.org/pub/packages/maven2/url mirrorOfcentral/mirrorOf /mirror /mirrors -- servers server idapache.snapshots/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server server idapache.releases/id username$USERNAME/username privateKey$PATH_TO_PRIVATE_KEY/privateKey directoryPermissions775/directoryPermissions filePermissions644/filePermissions /server /servers profiles profile idcargo-config/id properties cargo.tomcat5x.home$PATH_TO_TOMCAT_5/cargo.tomcat5x.home /properties /profile /profiles activeProfiles activeProfilecargo-config/activeProfile /activeProfiles /settings Expose a copy of known hosts to Maven 1 From cygwin, ssh to people.apache.org, save the public key if prompted, and exit cygwin will save the known hosts to your ~/.ssh folder, but the script cannot access it there (from Windows) 2 From cygwin (not Windows) create another .ssh folder at 3 Copy the known_hosts file to the new .ssh folder Tasks that need to be performed for each release 1 Update the POMs to remove "-SNAPSHOT" from the version 2 Commit the POM changes 3 Tag the release by making a SVN copy of the head or designated revision svn copy -r ## https://svn.apache.org/repos/asf/struts/struts2/trunk https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_# -m "Tag r## as Struts #.#.#" 4 Assemble the release mvn clean install site -P xwork,plugins,apps,all,pre-assembly cd assembly mvn assembly:assembly 5 Sign the release artifacts (in assembly/target/assembly/out) gpg --armor --output struts-#.#.#-all.zip.asc --detach-sig struts-#.#.#-all.zip openssl md5 struts-#.#.#-all.zip struts-#.#.#-all.zip.mdr 6 pscp the artifacts and signatures to people.apache.org:/www/builds/struts/#.#.# 7 Deploy the artifacts to our Maven repository mvn deploy -P apps,plugins,pre-assembly Prune any obsolete snapshots from p.a.o://www/people.apache.org/repos 8 Update the POMs to next version number and add the "-SNAPSHOT" suffix 9 Commit the POM changes 10 Deploy the new snapshot mvn -N install 11 Add the next version to our issue tracker for scheduling new features and fixes Resources Apache Guide To Release Management During Incubation Signing Releases Wendy's notes on Release Signing Apache Mirroring Guidelines Struts Release Instructions (upon which these instructions are based) Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request Unsubscribe or edit your notifications preferences
