Plan for Update Center 2.0 Release

Milestone	Build Date	QA Hand-off Date	Description	Reports	Status
Milestone 7	5/2/08	5/6/08	Misc. features/bug fixes	open issues , resolved issues, test report	Completed on schedule
Milestone 8	5/16/08	5/20/08	Misc. features/bug fixes, new IPS drop	open issues, resolved issues, test report, release notes	Completed on schedule
Milestone 9	5/30/08	6/3/08	Feature complete.	open issues, resolved issues ,test report	Completed on schedule
Milestone 10	6/13/08	6/17/08	Bug fixing.	open issues, resolved issues ,test report	Completed on schedule
Milestone 11	7/4/08	7/8/08	Bug fixing, final features.	open issues, resolved issues ,test report	Completed on schedule
Milestone 12	7/18/08	7/22/08	Beta Quality: Hard feature freeze (Zero P1s, Low P2s).	open issues, resolved issues, test report	Released to QA on July 24th
Milestone 13	Aug 3, 2008	Aug 5, 2008	Release Candidate #1 Build (Zero P1s, P2s, P3s).	open issues, resolved issues test report	Completed on schedule
Milestone 14	Aug 17, 2008	Aug 19, 2008	Release Candidate #2 Build (Zero P1s, P2s, P3s).	open issues, resolved issues test report	Released to QA on August 20th
Submit 508 Assessment	Aug 28, 2008			Accessibility status	Accessiblity tests completed on Aug 27 and 508 assessment submitted
Milestone 15	Sep 3, 2008	Sep 5, 2008	Will be integrated with GFv3	open issues, resolved issues test report	Completed on Sept 4.
B15-RC 1 build	Sep 10, 2008	Sep 12, 2008	Will be integrated with GFv3	open issues, resolved issues test report	Completed on schedule
RC 2 build	Sep 17, 2008	Sep 19, 2008	Will be integrated with GFv3 on 9/30	open issues, resolved issues, release notes , test report	Completed on Sept. 18
RC 3 build	Sep 24, 2008	Sep 26, 2008	Will be integrated with GFv3 build 28 on Oct 4	open issues, resolved issues , test report	Completed on schedule
RC 4 build	Oct 8, 2008	Oct 10, 2008	Will be integrated with GFv3 build 28a on 10/14	open issues, resolved issues, release notes, test report	Completed on Oct. 9
Sustaining TOI	Oct 14, 2008			slides	UC will be part of GFv3 TOI schedule; UC team will participate
Go/No-Go	Oct 16, 2008				JES PAC voted to approve.
Phase 5 Review	Oct 16, 2008				JES PAC (approved) - Oct 16, WAP PAC - Oct 20
GFv3 Prelude Release	Oct 29, 2008				GFv3 Prelude release will have the final UC 2.0 build
Multi-Language Release	Nov ??, 2008 (or sooner)				Will be integrated with GFv3 ML release on ??/?? (Need inputs from Julie to finalize this date)

For information about the 2.0 sustaining releases, see the 2.x planning page.

Release Overview

The primary objective of the Update Center Toolkit 2.0 production quality release is to provide bug fixes and necessary enhancements to the 2.0 preview release to make the toolkit suitable for use by revenue release products.

Requirements from the release have been derived from several sources:

• the Requirements Specification
• the Java Enterprise System System Release Document

After an analysis of these documents, any requirements that have not yet been met in the UC Toolkit have been recorded as issues in the updatecenter2.dev.java.net IssueTracker system. Each issue that is planned for this release is marked with a targeted milestone starting with "2.0-MS".

The changes for this release are summarized in the table below.

Area	Description
Improved Documentation (details)	Doc Plan Documentation improvements are planned for the following areas: * Online help in the updatetool GUI * Better support for information about the pkg CLI * Best practices and toolkit usage documentation on the UC2 wiki site
Fit and Finish (details)	These are miscellaneous changes to improve the overall usability of the toolkit and are by far the largest volume of changes for the release. Some of the more significant changes are: * Improvements to the installation progress dialog * Additional dialog for editing image properties * Additional information shown for installed packages * Accessbility support (508 compliance)
Download Size Reductions (details)	Where possible, the size of the UC2 Toolkit packages will be reduced.
Basic, Anonymous Usage Reporting (details)	Usage reporting is accomplished by gathering information from the requests that are made to the server when packages are downloaded. These changes improve the information that is available.
Robust Package Management (details)	This release includes updates to the IPS software to make package management more robust.
Validated Performance (details)	The 2.0 development effort includes server-side performance testing to validate that the UC2 toolkit can support the expected loads.
Basic Back Out of Updates (details)	For this release, the back out capability will consist of supporting the ability to install a previous version of a package.
Serviceability (details)	The release includes some minor improvements to serviceability, but the main serviceability effort for this release is to determine what serviceability improvements are needed for the future through the calculation of the serviceability index.
OOTB Desktop Notification Mac and Unix (details)	The previous release included desktop notification for Windows. These changes extend that support to Mac OS and Unix.
Localizations (details)	The GUI software will be modified to fully support internationalization and messages will be translated to 7 languages.
Tooling (details)	Changes to improve the ability to create packages.

Build Plan

The build date for a milestone is when features targeted for that milestone are expected to be completed and checked into the subversion repository. The build dates are all Fridays, and the code is expected to be completed by close-of-business on that day. On Monday morning, the nightly build from the weekend is installed by the engineering team and basic sanity testing is performed. The QA hand-off date is the Tuesday following the Friday build date. If there are stopper bugs that need to be fixed for the milestone, additional builds are done on Monday and Tuesday.

IPS Integration

Immediately after the completion of each milestone build, at the beginning of the development for the next milestone, a new IPS drop will be integrated. This drop will include the latest IPS code from the gate plus any IPS fixes that have been developed by the IPS team but not yet integrated into the IPS gate. This will allow the team to use the balance of the milestone development interval to make any code changes that are required because of the new IPS integration.

ARC Review

• One-pager for umbrella case planned for 5/16
• A separate ARC case needs to be scheduled for each of the other design specs

Planning TODO

• Specify if/when/how updates from the development towards the 2.0 release will be delivered to the GFv3 TP2 repository.
  • Suggested approach
    • Goals:
      • Deliver critical toolkit fixes to TP2 installed base.
      • Deliver useful toolkit features to TP2 installed base.
      • Use TP2 installed base as a providing ground for procedures and update capabilities of deployed UC installs leading up to RR quality release of toolkit.
      • Avoid having to maintain TP2 branch for an extended period of time. Backporting has a cost.
      • Gain practical experience in delivering toolkit features and fixes in a compatible manner.
      • Exercise new feature quickly as long as issues can also be addressed quickly.
    • Proposed Process
      • Every 2-3 weeks (frequency is TBD) qualify build of UC 2.0 and validate it as updates to the TP2 release
      • When a build is validated for promotion, tag it and publish the updates toolkit packages to the GF V3 TP2 repository
      • Consider aligning with GF V3 TP2 releases of updated packages
      • Exception process for critical fixes: Use latest branch as basis for delivering critical fixes out of band.
    • Dependencies
      • Installed base is actually looking for updates (new bootstrap invocations will receive new code anyway)
      • Developers maintain compatibility to the extent that updated packages work against TP2
      • Adequate test automation such that validating each candidate doesn't take too long

Milestones

• Open Issue Report (all milestones)
• Resolved Issue Report (all milestones)

Bug History Chart

This is a chart showing the number of open bugs for various priorities during the lifetime of the release development.

This page (revision-75) was last changed on 29-Oct-08 15:27 PM, -0700 by Mike Fitch.
This page was created on 17-Apr-08 08:04 AM, -0700 by TomMueller.

More info...