Imprudence:Release Checklist

This is a checklist of things the developers do to prepare a new version release.

Update the viewer version
These are the files you need to change when updating the viewer version:


 * linden/indra/newview/app_settings/viewerversion.xml
 * linden/indra/newview/Info-Imprudence.plist
 * linden/indra/newview/English.lproj/InfoPlist.strings
 * linden/indra/newview/res/viewerRes.rc

For beta releases, the test version should be "beta #" -- lowercase beta, space, then the number. For release candidates, it's "RC#". For full releases, it's empty.

Create the release notes on the wiki
The release notes page for a version is Release Notes/X.Y.Z-test_version, e.g. Release Notes/1.3.0-beta_5. Note the hyphen between the number versions and the test version, and that spaces in the test version are changed to underscores. The page name is case sensitive.

The top of the page should have "Imprudence X.Y.Z test version" with level 2 heading, e.g. . This is important for dividing the versions when the individual release notes pages are included into the main Release Notes page using the wiki's template system.

Jacek's preferred style for the release notes is to pick out some major points for a "Release Highlights" section at the top, followed by a "Known Issues" section, then a "Changes" section with subsections: "Features and Improvements", "Bug Fixes", "Other Changes". See Release Notes/1.3.0-beta_3 for an example.

Give credit/thanks for each change after each item in the notes. For things we did ourselves, Jacek prefers "Thanks, [first name]!". For things other people did, Jacek prefers "Thanks to [full name or project name] for this [feature/patch]!".

Update RELEASE_NOTES.txt
Once the release notes are done on the wiki, copy them to the RELEASE_NOTES.txt file and change the formatting for consistency with the existing notes. Jacek uses Emacs for this, especially its "fill" command to wrap the paragraphs nicely.