Differences between revisions 1 and 2
Revision 1 as of 2006-07-31 02:43:12
Size: 5369
Comment: Partially completed template proposal
Revision 2 as of 2009-09-20 21:52:51
Size: 5383
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 1. [http://shale.apache.org/releases.html Release Guidelines]  1. [[http://shale.apache.org/releases.html|Release Guidelines]]
Line 9: Line 9:
 2. [http://wiki.apache.org/incubator/SigningReleases Signing Releases]  2. [[http://wiki.apache.org/incubator/SigningReleases|Signing Releases]]
Line 11: Line 11:
 3. Apache [http://apache.org/dev/mirrors.html Mirroring Guidelines]  3. Apache [[http://apache.org/dev/mirrors.html|Mirroring Guidelines]]
Line 55: Line 55:
The Commons [http://jakarta.apache.org/commons/releases/prepare.html Preparation Guide] is a helpful preparation backgrounder, but Commons The Commons [[http://jakarta.apache.org/commons/releases/prepare.html|Preparation Guide]] is a helpful preparation backgrounder, but Commons
Line 58: Line 58:
Likewise, the [http://httpd.apache.org/dev/release.html HTTPD Release Guidelines] is a helpful "overall process" backgrounder, Likewise, the [[http://httpd.apache.org/dev/release.html|HTTPD Release Guidelines]] is a helpful "overall process" backgrounder,
Line 98: Line 98:
See also Commons [http://jakarta.apache.org/commons/releases/release.html Step-by-Step Guide] See also Commons [[http://jakarta.apache.org/commons/releases/release.html|Step-by-Step Guide]]
Line 114: Line 114:
Voting thread is [http://www.nabble.com/-VOTE-Struts-Shale-v1.0.2-Quality-t1328711.html here] Voting thread is [[http://www.nabble.com/-VOTE-Struts-Shale-v1.0.2-Quality-t1328711.html|here]]

(Up to ReleasePlans)

Shale X.Y.Z Release Plan

Info

  1. Release Guidelines

  2. Signing Releases

  3. Apache Mirroring Guidelines

Release Manager

The release manager is XXXXX YYYYY

Special Issues

FIXME - Identify any special issues related to this release, or remove it if there are none.

Outstanding Issues Review

The following links perform live queries against the JIRA issues database for Shale (for bugs, RFEs, and tasks, respectively), so the content will change as issues are added and addressed.

Outstanding Bug Review

FIXME - link to a JIRA query

FIXME - list any commentary on specific issues listed by the previous query

Outstanding Enhancements Review

FIXME - link to a JIRA query

FIXME - list any commentary on specific issues listed by the previous query

Outstanding Tasks Review

FIXME - link to a JIRA query

FIXME - list any commentary on specific issues listed by the previous query

Preparation Checklist

FIXME - all following text was just copied from the 1.0.2 release plan and needs to be customized.

#

Description

Status

1.

Announce plan to dev@ list

(./)

2.

Review/Complete Remaining Development Tasks

(./)

3.

Review/Resolve Outstanding Bugs

(./)

4.

Update Release Notes

(./)

5.

Check Dependencies

(./)

6.

Update to version 1.0.2 default.properties, project.xml, build/maven2/*.pom

(./)

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.

Dependency versions for this release:

Dependency

Version

Status

Used In

Commons BeanUtils

1.7.0

Released

core, clay

Commons Chain

1.0.0

Released

core, clay

Commons Digester

1.7.0

Released

core, clay

Commons Logging

1.0.4

Released

core, clay, test, usecases

Commons Validator

1.2.0

Released

core

JavaServer Faces

1.1

Released

core, clay, test, usecases

Spring Framework (Optional)

1.2.2

Released

core

Struts Tiles Standalone

---

Struts Sandbox

core

HtmlUnit (Optional)

1.6 or 1.7

Released

test, usecases

Because this is a test build release, a dependency on an unreleased component is acceptable.

Testing Checklist

Testing Summary

#

Description

Completed

1.

Run Unit Test targets against JSF RI

(./)

2.

Run Unit Test targets against MyFaces

(./)

3.

Run Use Cases system integration tests (see below)

(./)

4.

Play test bundled applications

(./)

Use Cases System Integration Tests

#

J2SE Version

Tomcat Version

JSF Version

Status

1.

J2SE 1.4.2_10

Tomcat 5.0.30

JSF RI 1.1_01

(./)

2.

J2SE 1.4.2_10

Tomcat 5.0.30

MyFaces 1.1.1

(./)

3.

J2SE 1.5.0_06

Tomcat 5.0.30

JSF RI 1.1_01

(./)

4.

J2SE 1.5.0_06

Tomcat 5.0.30

MyFaces 1.1.1

(./)

5.

J2SE 1.5.0_06

Tomcat 5.5.15

JSF RI 1.1_01

(./)

6.

J2SE 1.5.0_06

Tomcat 5.5.15

MyFaces 1.1.1

(./)

Test Build Checklist (A)

See also Commons Step-by-Step Guide

#

Description

Completed

A1.

Tag release in svn: STRUTS_SHALE_1_0_2

(./)

A2.

Run Release Target

(./)

A3.

Upload Distribution to cvs.apache.org:/www/cvs.apache.org/dist/struts/shale/v1.0.2

(./)

A4.

Post release-quality vote on dev@ list

(./)

Vote (A)

PMC Member

Quality

Wendy Smoak

Alpha

Gary VanMatre

Alpha

Craig McClanahan

Alpha

Niall Pemberton

Alpha

Voting thread is here

If release vote fails, including for a lack of quorum, remove from dist folder.

Point Release Checklist (B)

#

Description

Completed

B1.

Create Sums and Sign Distributions [2]

(./)

B2.

Request new Bugzilla version level (1.0.2)

(./)

B3.

Update "Acquiring" page on website and Test Downloads

(./)

Vote (B)

PMC Member

Quality

Voting continues until a GA or "withdraw" vote passes, or there is a subsequent release.

General Availability Checklist (C)

#

Description

Completed

C1.

Copy Distribution to Mirrored Directories [3]

_

C2.

Deploy JARs to Apache Java-Repository

_

C3.

After 24 hours, update "Acquiring" page on website

_

C4.

Post an announcement to lists and website

_


ReleasePlanTemplate (last edited 2009-09-20 21:52:51 by localhost)