(Up to ReleasePlans)

Shale 1.0.0 Release Plan

(This page was copied from the Struts Wiki, where the actual planning effort took place.)

Info

  1. Struts Release Guidelines

  2. Signing Releases

  3. Apache Mirroring Guidelines

Release Manager

The release manager is Craig McClanahan

Special Issues

This release is an interim test build release of Shale technology. As such, you should assume that the APIs are still evolving and subject to change. For a stability rating on each API, see http://struts.apache.org/struts-shale/api-stability.html for more information.

Outstanding Bug Review

ID

Summary

Component

Status

35066

Serious issue with dialog state

dialog

LATER[1]

35839

Clay processes components inside HTML comments

clay

LATER[2]

37024

No clay component configuration for MyFaces Tomahawk

clay

LATER[3]

37120

IFrame does not work properly inside Shale dialog

dialog

LATER[4]

37361

"categories" selectManyCheckBox in usecases fails

example

REMIND[5]

37615

"Clay attributes are not using xml namespaces

clay

RFE[6]

37643

Add documentation for "tiles" and "remoting" features

docs

RFE[6]

[1] The dialog facility is in need of improved functionality for handling multiple simulteously active dialogs, and dealing with back buttons. I propose to make this a significant focus in a 1.0.1 milestone release.

[2] The proposed solution to this issue is to cut-n-paste the HTML parser that Tapestry uses for reading templates. Before going that way, it would be appropriate to see if the Tapestry developers were interested in abstracting out this code (perhaps to a commons project) so that it could be shared more easily.

[3] The Shale contribution to addressing this issue is to ensure that META-INF/clay-config.jar resources in JAR files loaded as part of the application are automatically loaded. The actual configuration resources for a given component library such as Tomahawk, however, should be provided by the component library itself rather than by Shale.

[4] Will be addressed as part of the overall support for multiple simultaneously active dialogs.

[5] This is actually a MyFaces imlementation bug (see issue MYFACES-829). Resolving as REMIND to remember to mention this in the Shale 1.0.0 release notes.

[6] RFE to be reviewed for a subsequent release.

Remaining Development Tasks

Description

Status

Add API stability rating matrix to overview page for Core Library

(./)

Add "release" target to top level build script

(./)

Preparation Checklist

#

Description

Status

1.

Announce plan to dev@ list; link from roadmap page

(./)

2.

Complete Remaining Development Tasks

(./)

3.

Review/Resolve Outstanding Bugs

(./)

4.

Update Release Notes

(./)

5.

Check Dependencies

(./)

6.

Update to version 1.0.0 build.xml, project.xml, and the MANIFEST.MF

_

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.1.4

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

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.28

JSF RI 1.1_01

(./)

2.

J2SE 1.4.2_10

Tomcat 5.0.28

MyFaces 1.1.1

(./)

3.

J2SE 1.5.0_05

Tomcat 5.0.28

JSF RI 1.1_01

(./)

4.

J2SE 1.5.0_05

Tomcat 5.0.28

MyFaces 1.1.1

(./)

5.

J2SE 1.5.0_05

Tomcat 5.5.12

JSF RI 1.1_01

(./)

6.

J2SE 1.5.0_05

Tomcat 5.5.12

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_0

(./)

A2.

Run Release Target

(./)

A3.

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

(./)

A4.

Post release-quality vote on dev@ list

(./)

Vote (A)

PMC Member

Quality

Craig McClanahan

Alpha

Ted Husted

Alpha

Wendy Smoak

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.0)

_

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

_


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