Plash development

Tasks are tracked on RoadMap as "stories". Each story should have a status of "planning", "in progress" or "done".

Bugs are tracked as pages underneath PlashIssues. A bug is marked with CategoryFixed when it is believed to be fixed.

ContinuousIntegration rebuilds Plash hourly on various Ubuntu/Debian versions.

Steps for making a new release

Check that all story pages are up-to-date, have the correct status and don't need more work doing
Work out which bugs will and won't be fixed
Building:
- Make sure that ContinuousIntegration and AutoBuildPackages cover the latest version of Ubuntu -- yes, upto hardy
- Build Plash using chroots created from scratch using BuildTools
- Ensure there are no unchecked-in changes for BuildTools
- Make sure source and binary packages are lintian and linda clean (build tools do not always flag their warnings as errors) -- yes, but ignoring missing man page warnings
Run through ManualTests
Write release announcement e-mail; create a page along the lines of PlashRelease1.18 -- PlashRelease1.19
Update version numbers in source
- debian-template/changelog. This could have X.XX.svn in SVN. It gets overwritten by build system anyway.
- configure.in: version in AC_INIT. This is supposed to get compiled in, but not all command line tools display it.
Create tags:
- Tag of trunk in SVN -- plash-1.19
- Tag glibc in Git (have not done this before!) -- plash-glibc-1.19
Ensure that DownloadPackages is up-to-date
Ensure that BuildingFromSource is up-to-date
Announce on Plash mailing list
Announce on cap-talk mailing list
Announce on http://freshmeat.net
Add entry to PlashReleases
Add entry to "News" section of FrontPage
Upload packages to Launchpad PPA (personal package archive)
- Submit package to Ubuntu Universe
Update release information on Wikipedia page