Pluto 1.0.1-rc2 Release

Thanks to the Struts team for their Wiki release template.

Info

A first stab at an rc2 release plan

Release Manager

The release manager is NickLothian

Issues

* Waiting for Tomcat 5.5.x to recieve a GA label or the Cross Context Session fix in Tomcat to be migrated to Tomcat 5.0.x and subsequently released. RESOLVED, Tomcat 5.5.4 is now released. "download here".

Outstanding Bug Review

ID

Summary

Component

Prevents Release

PLUTO-87

The page fragment name is not encoded

Portal

NO - trivial issue with good workaround

PLUTO-86

Pluto 1.1: portlet context never initialized for portlet session

Pluto 1.1

NO - Pluto 1.1 bug

PLUTO-82

PortalURL tied to single host specified in properties

Portal

NO - enhancement

PLUTO-71

Login link on Release Candidate home page is inappropriate

Portal

NO - probably not a bug, waiting for further comments

PLUTO-42

control.getPIDValue(); always returns "", PORTLET_ID is never set

Container

NO - no one is sure how to fix this

PLUTO-38

user profile attribute support

Container

NO - enhancement request

PLUTO-37

custom portlet modes / window states support

Portal

NO - enhancement request

PLUTO-20

PortletControlParameter's getPIDValue and setPortletID disagree

Portal

NO - related to PLUTO-42

Dependency versions for this release

Dependency

Version

Status

portlet-api

1.0

Required by spec

servletapi

2.3

Required by spec

castor

0.9.5

Current version is 0.9.5.4

commons-logging

1.0.4

Current

commons-cli

1.0

Current

xerces

2.3.0

Current version is 2.6.2

xml-apis

2.0.2

?

Preparation Checklist

#

Description

Comments

Completed

0.

Announce plan to dev@ list; link from roadmap page

See http://nagoya.apache.org/eyebrowse/ReadMsg?listName=pluto-dev@portals.apache.org&msgNo=2128

2 Dec 04

1.

Review/Resolve Outstanding Bugs

Review all outstanding issues and make a descision on whether they should be resolved for this release. Add those that should be resolved to the above bug list. If nothing else, at least acknowledge they are issues or resolve them as invalid.

02 Dec 04

3.

Review Dependencies and make sure optimal ones have been released.

Castor, Xerces and xml-apis should be upgraded, but not in the RC2 timeframe

01 Dec 04

2.

Update Release Notes

Done (NickLothian)

01 Dec 04

3.

Check Dependencies

Done (NickLothian)

01 Dec 04

4.

Update project.xml to version 1.0.1-rc2 build.xml

Done (NickLothian)

01 Dec 04

Point Release Checklist (A)

See also Commons Step-by-Step Guide

#

Description

Completed

A1.

Tag distribution in svn: release-1.0.1-rc2

5 Dec 04

A2.

Run distribute:all maven goal to generate distributions

5 Dec 04

A3.

Upload test build to cvs.apache.org:/www/cvs.apache.org/dist/portals/pluto/v1.0.1-rc2

6 Dec 04 - See http://cvs.apache.org/dist/portals/pluto/v1.0.1-rc2/

A4.

Announce test-build on dev@ and pmc@ lists only

6 Dec 04

A5.

Post release-quality vote on dev@ list

_

Vote

A6.

If vote fails (including lack of quorum), remove test-build cvs.apache.org

_

A7.

If vote passes, update "Acquiring" page on website

_

A8.

If vote passes, deploy JAR to Apache Java-Repository

_

General Availability Checklist (B)

#

Description

Completed

B1.

Create Sums and Sign Distributions

_

B2.

Copy Distribution to Mirrored Directories

_

B3.

Update "Acquiring" page on website and Test Downloads

_

B4.

Post an announcement to lists and website

_

B5.

Request new Bugzilla version level (1.2.5)

_

Pluto/PlutoRelease101Rc2 (last edited 2009-09-20 23:46:34 by localhost)