Developers using Linux workstations can skip over the references to PuTTY and Cygwin

Each time

(There are also one-time setup instructions)

To keep this list current, it is strongly recommended that release managers refer to and follow this list each time a distribution is created. If any of the steps need to be amended, then please update the list.

svn co https://svn.apache.org/repos/asf/struts/struts2/trunk STRUTS_#_#_#

svn co https://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_2_0_X STRUTS_#_#_#

svn copy -r ###### 
  https://svn.apache.org/repos/asf/struts/struts2/trunk 
  https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_# 
  -m "WW-#### Tag r###### as Struts #.#.#" 

mvn clean install site -P all,alljars,pre-assembly,j4
cd assembly 
mvn clean assembly:assembly

mvn deploy -P release,all,alljars,pre-assembly -Dgpg.passphrase="$PASSPHRASE"

gpg --armor --output struts-#.#.#-all.zip.asc --detach-sig struts-#.#.#-all.zip 
openssl md5 < struts-#.#.#-all.zip > struts-#.#.#-all.zip.md5

mvn clean install site -P all,alljars,pre-assembly,j4
mvn site-deploy -Pall 

One time

Create and install a SSH key (CygWin/Linux)

• See http://rcsg-gsir.imsb-dsgi.nrc-cnrc.gc.ca/documents/internet/node31.html

Create and install a SSH key (Windows)

In either case

• Note that the .ssh folder on p.a.o is hidden, but you can still cd to it, or see it using ls -a
• Be sure that the permissions for the authorized_keys files is set to -rw-r--r-- (to see the permissions use ls -l). To remove the "group" or "other" permissions, use chmod go-w authorized_keys

Create a PGP key

Update Maven settings for our servers

<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>
        <id>ggi-project.org</id>
        <url>http://ftp.ggi-project.org/pub/packages/maven2</url>
        <mirrorOf>central</mirrorOf>
      </mirror>
    </mirrors -->
    <servers>
       <server>
          <id>apache.snapshots</id>
          <username>$USERID</username>
          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
          <directoryPermissions>775</directoryPermissions>
          <filePermissions>644</filePermissions>
       </server>
       <server>
          <id>struts-staging</id>
          <username>$USERID</username>
          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
       </server>
       <server>
          <id>apache-site</id>
          <username>$USERID</username>
          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
       </server>       
    </servers>
   <profiles>
       <profile>
        <id>cargo-config</id>
         <properties>
            <cargo.tomcat5x.home>$CATALINA_HOME</cargo.tomcat5x.home>
         </properties>
      </profile>
      <profile>
         <id>struts-staging</id>
         <repositories>
           <repository>
             <id>struts-staging</id>
             <url>http://people.apache.org/builds/struts/m2-staging-repository</url>
             <snapshots><enabled>false</enabled></snapshots>
             <releases><enabled>true</enabled></releases>
           </repository>
          </repositories>
        </profile>   
   </profiles>
   <activeProfiles>
      <activeProfile>cargo-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

Increase Memory Settings for Maven

To complete a full build and all the tests, it may be neccesary to increase the amount of memory available to Maven. The simplest thing is to set an environment variable.

• MAVEN_OPTS=-Xmx512m or even MAVEN_OPTS=-Xmx1024m

Skip Tests

On occasion, it can be helpful to skip the unit tests to be sure the buid otherwise completes. From the command line, add

• -Dmaven.test.skip=true

Do not do this when building a release!

Resources

• Apache Struts Release Guidelines
• Struts Maintenance Guide for Maven
• Signing Releases
• Wendy's notes on Release Signing
• Apache Mirroring Guidelines

Retagging

If a tagged build needs to be retagged, be sure to delete the old tag first.

svn delete https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_# -m "WW-### Removing first try at 2.#.#."

Interim Notes on Cobbling a Distribution

Before signing

• There's a bug in the current Maven GPG. The workaround is, before signing, under each application's target folder, copy the application's WAR as a JAR. This should go away in the next GPG release.

Amending a log entry

If the commit was fine, but the log was wrong, updating the log entry is easy. For example,

> svn propset --revprop -r 504523 svn:log "WW-1715 Branch for 2.0.x at Struts 2.0.6-SNAPSHOT r504196"
> property 'svn:log' set on repository revision 504523

See svn help propset for more.

Sample Test Build Announcement

Test builds are only announced to the dev list. Announcements to the user list can only be made pursuant to a release vote with the consent of the PMC.

The test build of Struts 2.0.6 is available.

No determination as to the quality ('alpha,' 'beta,' or 'GA') of Struts 2.0.6 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build.

Release notes:

• [LINK]

Distribution:

• http://people.apache.org/builds/struts/#.#.#/

Maven 2 staging repository:

• http://people.apache.org/builds/struts/#.#.#/m2-staging-repository/

We appreciate the time and effort everyone has put toward contributing code and documentation, posting to the mailing lists, and logging issues.

Sample Release/Quality Vote

The Struts #.#.# test build is now available.

Release notes:

• http://struts.apache.org/2.x/docs/release-notes-###.html

Distribution:

• http://people.apache.org/builds/struts/#.#.#/

Maven 2 staging repository:

• http://people.apache.org/builds/struts/#.#.#/m2-staging-repository/

Once you have had a chance to review the test build, please respond with a vote on its quality:

[ ] Leave at test build
[ ] Alpha
[ ] Beta
[ ] General Availability (GA)

Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s.

The vote will remain open for at least 72 hours, longer upon request. A vote can be amended at any time to upgrade or downgrade the quality of the release based on future experience. If an initial vote designates the build as "Beta", the release will be submitted for mirroring and announced to the user list. Once released as a public beta, subsequent quality votes on a build may be held on the user list.

As always, the act of voting carries certain obligations. A binding vote not only states an opinion, but means that the voter is agreeing to help do the work

Sample Release Announcement

The Apache Struts group is pleased to announce that Struts 2.0.6 is available as a "#####" release. [[The Beta designation indicates that we believe the distribution needs wider testing before being upgraded to a "General Availability" release. Your input is essential.] The GA designation is our highest quality grade. ]

http://struts.apache.org/download.cgi#struts###

The release is also available from the central Maven repository under Group ID "org.apache.struts".

The #.#.x series of the Apache Struts framework has a minimum requirement of the following specification versions:

• Java Servlet #.# and JavaServer Pages (JSP) #.#
• Java 2 Standard Platform Edition (J2SE) #.#

The release notes are available online at:

• http://struts.apache.org/2.x/docs/release-notes-###.html

Should any issues arise with your use of any version of the Struts framework, please post your comments to the user list, and, if appropriate, file a ticket with JIRA.

– The Apache Struts group.

Fast-Tracking an Important Security Release

• When a serious security issue arises, we should try to create a #.#.#.1 branch from the last GA release, and apply to that branch only
  the security patch.
• If the patch first applies to XWork, or some other dependency, implore the other group to do the same, to avoid side-effects from other changes.
• If the release manager would like to "fast track" a vote, so as to make a security fix available quickly, the preferred procedure is to
  • Include the term "fast-track" in the subject, as in [VOTE] Struts 2.0.9.1 quality (fast track)
  • In the vote message, specify voting terms like:

    The Struts #.#.#.1 test build is now available.

    Release notes:

    • http://struts.apache.org/2.x/docs/release-notes-####.html

    Distribution:

    • http://people.apache.org/builds/struts/#.#.#.1/

    Maven 2 staging repository:

    • http://people.apache.org/builds/struts/#.#.#.1/m2-staging-repository/

    Once you have had a chance to review the test build, please respond with a vote on its quality:

    [ ] Leave at test build
    [ ] Alpha
    [ ] Beta
    [ ] General Availability (GA)

    Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s.

    This is a "fast-track" release vote. If we have a positive vote after 24 hours (at least three binding +1s and more +1s than -1s), the release may be submitted for mirroring and announced to the usual channels.

    The website download link will include the mirroring timestamp parameter [1], which limits the selection of mirrors to those that have been refreshed since the indicated time and date. (After 24 hours, we *must* remove the timestamp parameter from the website link, to avoid unnecessary server load.) In the case of a fast-track release, the email announcement will not link directly to <download.cgi>, but to <downloads.html>, so that we can control use of the timestamp parameter.

    [1] <http://apache.org/dev/mirrors.html#use>