Pluto 1.0.1-rc3 Release
Thanks to the Struts team for their Wiki release template.
Info
The RC3 Release Plan. Planned for June 2005. A build was posted on 6/25 and announced to the dev list. It is available here: http://people.apache.org/~ddewolf/1.0.1rc3/
If this build is found to be stable, it will be considered 1.0.1-rc3 and will be released as such in the near future.
Release Manager
The release manager is DavidDeWolf
Issues
Outstanding Bug Review
ID |
Summary |
Component |
Prevents Release |
Comments |
PLUTO-110 |
Deployer Strips load-on-startup elements |
Deployer |
Fixed |
03/09/2005 |
PLUTO-103 |
Admin portlet application for deploying custom portlets |
Portal |
Fixed |
02/20/2005 |
PLUTO-100 |
getPortletOutputStream cannot handle multi-byte character |
Container |
Fixed |
02/09/2005 |
PLUTO-97 |
Custom Modes and Window States don't work with Tags |
Tags |
Fixed |
02/15/2005 |
PLUTO-92 |
Deployer strips existing mime-mapping elements out of web.xml |
Deployer |
Fixed |
03/09/2005 |
PLUTO-82 |
PortalURL tied to single host specified in properties |
Portal |
Fixed |
01/22/2005 |
PLUTO-87 |
The page fragment name is not encoded |
Portal |
No |
Trivial with Work Around |
PLUTO-71 |
Login link on Release Candidate home page is inappropriate |
Portal |
Fixed |
02/10/2005 |
PLUTO-42 |
control.getPIDValue(); always returns "", PORTLET_ID is never set |
Container |
Fixed |
03/09/2003 |
PLUTO-38 |
user profile attribute support |
Container |
No |
Enhancement Request |
PLUTO-37 |
custom portlet modes / window states support |
Portal |
Fixed |
02/15/2005 |
PLUTO-20 |
PortletControlParameter's getPIDValue and setPortletID disagree |
Portal |
Invalid |
Invalid |
Dependency versions for this release
Dependency |
Previous Version |
Target Version |
Upgrade Required |
Status |
Comments |
portlet-api |
1.0 |
_ |
No |
Required By Spec |
_ |
servletapi |
2.3 |
_ |
No |
Required by spec |
_ |
castor |
0.9.5.0 |
0.9.5.4 |
No |
Upgrade Complete |
0.9.5.3 |
commons-logging |
1.0.4 |
1.0.4 |
No |
Current |
_ |
commons-cli |
1.0 |
1.0 |
No |
Current |
_ |
xerces-xercesImpl |
2.3.0 |
2.6.2 |
Yes |
Upgrade Complete |
_ |
xerces-xercesParserAPIs |
_ |
2.6.2 |
Add |
Added |
_ |
xml-apis |
2.0.2 |
_ |
Remove |
Removed |
_ |
Preparation Checklist
Description |
Comments |
Completed |
|
0. |
Announce plan to dev@ list; link from roadmap page |
Done |
12/26/2004 |
1. |
Review/Resolve Outstanding Bugs |
Completed |
06/24/2004 |
2. |
Review Dependencies and make sure optimal ones have been released. |
Completed |
12/27/2004 |
3. |
Update Release Notes |
Completed |
06/24/2005 |
4. |
Update POM and Dependencies to version 1.0.1-rc3 |
Complete |
12/27/2004 |
Point Release Checklist (A)
See also Commons Step-by-Step Guide
Description |
Completed |
|
A1. |
Tag distribution in svn: release-1.0.1-rc3 |
06/24/2005 |
A2. |
Run distribute:all maven goal to generate distributions |
06/24/2005 |
A3. |
Upload test build to cvs.apache.org:/www/cvs.apache.org/dist/portals/pluto/v1.0.1-rc3 |
06/30/2005 |
A4. |
Announce test-build on dev@ and pmc@ lists only |
06/30/2005 |
A5. |
Post release-quality vote on dev@ list |
06/30/2005 |
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. |
Add a new JIRA Label for the Next version |
_ |