Struts 1.3.7 Release

Info

  1. Struts Release Guidelines 2. Signing Releases
    3. Apache Mirroring Guidelines

Release Manager

The release managers is Paul Benedict

How to Help

Everyone in the Struts community, users, developers, and committers, is encouraged to test a release, report any issues, and post to dev@ any comments on the overall quality of the release.

The Struts 1.3.7 distribution will be available here: http://people.apache.org/builds/struts/1.3.7

To help everyone get started with Struts 1.3.7, here are the simplest installation instructions that can possibly work:

  • Download the Struts 1.3.6 distribution (when it is available)
  • Extract the distribution to a likely location (/opt/struts-1.3.6).
  • If possible, try the JARs in a 1.2.x application that already compiles WITHOUT deprecations.
  • Deploy and play-test the example applications from the /webapps folder to your web container
    • If you see any error messages, please do a quick search of the mail archives and/or post them on the Dev list, and if they appear to be newly introduced issues, a JIRA tickets will need to be created so we can track and resolve the issue as quickly as possible.
      • Vesion 1.3.7 is tagged. The issue can be logged against 1.3.7, but the fix would happen in 1.3.8 or later.
  • Change to the /docs directory and click-thru the documentation. If you notice anything awry, follow the "error messages" advice.

To test building Struts 1.3.7

  • Install Java 1.5 and set JAVA_HOME
  • Install Maven 2 and set MAVEN_HOME ** http://wiki.apache.org/struts/StrutsMaintenanceMaven
  • Change to the new folder (e.g., /opt/struts-1.3.7/src)
  • $ mvn install
  • Wait five minutes or more for Maven to download and build everything
  • $ cd assmbly
  • $ mvn assembly:assembly
  • The distribution will be deposited in 'assembly/target/assembly/out'.
  • If you encounter any problems with the build, follow the "error messages" advice.
  • Oh, and THANK YOU for your help. (smile)

Issues

TO DO

Preparation Checklist

Description

Status

1.

Announce plan to dev@ list

(tick)

2.

Review/Resolve Outstanding Bugs

(tick)

3.

Update Release Notes

(tick)

4.

Check Dependencies

(tick)

The Commons Preparation Guide is a helpful preparation backgrounder, but Commons uses the "beta/release-candidate/final" process.

Likewise, the HTTPD Release Guidelines is a helpful "overall process" backgrounder, but HTTPD does not use a test-build stage.

External Dependency versions for this release:

Dependency

Version

Status

Used In

Antlr

2.7.2

Released

Struts Validator

Bean Scripting Framework

2.3.0

Released

Scripting

Commons BeanUtils

1.7.0

Released

core (ActionServlet, configuration, DynaActionForm)

Commons Chain

1.1

Released

core (RequestProcessor)

Commons Digester

1.8

Released

core (ActionServlet, configuration)

Commons FileUpload

1.1.1

Released

Struts Upload

Commons IO

1.1

Released

Required by Commons FileUpload

Commons Logging

1.0.4

Released

core (logging all over)

Commons Validator

1.3.1

Released

Struts Validator

Jakarta Oro

2.0.8

Released

Commons Validator

Testing Checklist

Testing Summary

Description

Completed

1.

Run Unit Test targets

(tick)

2.

Run Cactus Tests (see below)

NA

3.

Play test applications (TC 5.5.x)

(tick)

Note: Cactus tests are not working and have been moved to the sandbox.

Test Build Checklist (A)

See also Commons Step-by-Step Guide

Description

Completed

A0.

Update all pom.xml files to omit "-SNAPSHOT"

(tick)

A1.

Tag release in svn: STRUTS_1_3_7

(tick)

A2.

Check out a clean copy using the tag created in A1 and see StrutsMavenRelease

(tick)

A3.

Deploy Test Build to people.apache.org: /www/people.apache.org/builds/struts/m2-staging-repository

(tick)

A4.

Upload distributions to people.apache.org:/www/people.apache.org/builds/struts/v1.3.x

(tick)

A5.

Refresh default website at /1.x and create archival copy at /1.3.5

(tick)

A6.

Update all pom.xml files to "1.3.8-SNAPSHOT"

(tick)

A7.

Create a new JIRA version level (1.x next)

(tick)

A8.

Announce the Test Build on dev@ only

(tick)

A9.

Post release-quality vote on dev@ list

(tick)

Vote (A)

1

GA

1

Beta

  • No labels