Zero Point Three Non-Code Release Process

This page is a strawman for describing the process for pulling together all of the non-code pieces for the 0.3 release.

Most of the pieces are documentation, described on the checklist below.

1. Examine the user experience for developers.
2. Examine the checklist to determine what is and what is not applicable for the release. This needs to happen several times over the release cycle, first at the end of the previous release cycle, somewhere in the middle, again about two weeks before release, and as needed after that. (Ducky/Pieter)
3. Figure out if there are any things that are not on the checklist that should be. Add them to the checklist. This should happen at the same time as the "examine the checklist" step. (Ducky/Pieter)
4. Add detailed tasks to Bugzilla. This should happen as early as possible.
5. Do the tasks. (as appropriate)

In addition, someone needs to arrange for the party. This should happen about two days before the release.

• Order food for delivery. (Blue)
• Make sure that there are adequate utensils, plates, cups, napkins, etc. (Blue)
• Determine who outside of OSAF staff and volunteers should get an invitation to the party. This list could include press, analysts, distinguished guests, and other "outsiders" if appropriate. (Mitch/Pieter)
• Remind people -- particularly those who don't regularly come into the office -- that a party is coming up. (NA?)
• Order Tchotchkes (Pieter, Bug:1251)

Release Documentation Process

The entire user experience for developers needs to be examined. That will affect the list below. Note that the list below should also be visible in Bugzilla as the dependency tree for Bug 1244.

The following documents need to be created or updated for 0.2:

What	Responsibility	Reviewer/Involved	Dependency	Where	Status	Bug#
Distribution	Morgen	Ducky				Bug:1221
README in distribution	Ducky		What's new, known bugs, where to find, release purpose, how to get involved	distro		Bug:1222
What's New	Morgen	Ducky,Chao		distro, wiki		Bug:1252
KnownMajorBugs	Ducky	Katie, Andi	final bug list	distro, wiki		Bug:1253
Where to find help	Ducky		locations	distro, wiki		Bug:1254
Release info/purpose summary	Chao		none	wiki		Bug:1196
How to get involved doc	Ducky, Mitchell	Katie?	Bug:1196	distro, wiki	incorporated into README	Bug:1255
BuildingChandlerDesktop	Morgen			wiki		NA
Download page	Morgen			Web		NA?
Download testing	Heikki		final binaries	Web		Bug:1304
Checksums for downloads	Heikki	Morgen	none -- can be done later	Web		Bug:1304
Update ChandlerDesktopSource	Morgen or Markie			wiki		NA
Developer documents	Responsibility	Reviewer				Bug:1256
GettingChandlerSource	Morgen	Ducky		wiki		NA
CpiaZeroPointThreeStatus	John	Mitch, Jed, Katie		wiki		Bug:1257
Parcel XML doc	Morgen	Andi, Ted, Heikki, Mark		wiki		Bug:1256
General technical overview	Katie	Chao, John, Ted		wiki		Bug:1259
Busy Developer's Guide	Ted	John, Mark		wiki, web		NA
Content model docs	Jeffrey, Morgen			wiki		Bug:1306
Notification model docs	Stuart	John, Andi		wiki		Bug:1260
Agent docs (clean up enough to not be misleading)	Pav	John, Andi		wiki		Bug:1307
Update or delete arch doc	?				Moved to Jungle, all links killed; web page not removed	??
End-user documents	Ducky
Splash screen	Katie, Mimi			code	done enough, but possible update	Bug:1205
About Chandler (HTMLify README)	Chao		README	code		Bug:1302
About ZaoBao	Ducky			code		Bug:1301
Higher-level documents	Chao
Update Introduction for Developers	Pieter, Ducky		Bug:1196, Bug:1233, Bug:1259	wiki		Bug:1261
ChandlerTimeline	Chao			wiki
Vision doc	Pieter					Bug:790
Product ProductFAQ?	Pieter					Bug:796
0.4 Docs	Chao
0.4 info	Chao		none	wiki	requires major polishing	Bug:1312
ChandlerLandscapeProposal	Mimi			wiki
ItemCollection	Mitch			wiki
Canoga UsersAndGroupsDesign2004	BrianDouglasSkinner			wiki
CanogaSecurityDesign	Chao	Heikki		wiki
CanogaSharingDesign20040419	Chao			wiki

CanogaSharingInitiation	Chao			wiki
SharingAView	Mimi			wiki
Announcements	Pieter
Announcements	Pieter		feature list	Web, RSS, mailing lists		Bug:1262
IRC announcement	Ducky		release	IRC		Bug:1263

The following links need to change to the 0.3 release:

• release info
• download link
• tech docs link

Schedule

• Skeleton wiki pages should exist on T minus 10 days (so can build navigation structure)
• The docs should be ready by T minus one week so that they can get an internal review.
• Pieter should get the distribution docs at 3 days before code freeze for copy-editing.
• Documentation complete 24 Feb 2004.
• Final release currently scheduled at 26 Feb 2004.

See ZeroPointTwoNonCodeReleaseActionItems

-- DuckySherwood - 05 Feb 2004