Hey, here's a draft release-reminder email template, as discussed with
aj on #email@example.com
No need to use it, but aj asked what sort of thing might be useful to
encourage people to fix RC bugs, and I think this would do it for me.
One mail per source package per maintainer (I'd send it to the
Maintainer: as well as all the Uploaders:, just in case the Maintainer:
This mail is sent as part of the Sarge release process. Please don't ignore
it. If for some reason you're unable to take action regarding the issues
outlined below, please inform @SOME-EMAIL-ADDY-HERE@.
One of your sources packages, @SOURCEPACKAGE@, has been found to have one or
more release-critical bugs. Specifically, the version of the package that's in
the Sarge repository has one or more release-critical bugs filed against it.
These are outlined in the following paragraph (more text follows the outline):
Package: @PACKAGE@ (debian/@ARCHIVE@)
Explanation for bug tags:
--- Start bug list
123456 [ + ] @BUGDESC@
123456: Last activity @LASTDATE@
123457 [ ] @BUGDESC@
123457: Last activity @LASTDATE@
--- End bug list
In order to release this package with Sarge, action must be taken regarding
the above bugs. There are several options available:
1. Fix the bug:
After fixing the bug, upload the new package to Sid. No other action is
2. Downgrade the bug:
Only downgrade the bug to Important or lower if the bug isn't, in fact,
3. Tag the bug sarge-ignore:
You may only mark a release-critical bug as "sarge-ignore" after
discussion with the release management team, available through
firstname.lastname@example.org. For a standard list of
release-critical bugs which are exempt from negative consideration for
Sarge, read http://people.debian.org/~ajt/sarge_rc_policy.txt . Read
this text before contacting email@example.com.
If you are unable to take any of the above actions with respect to your bugs,
please contact @SOME-EMAIL-ADDRESS-HERE@. If no action is taken, the package
may be removed from Sarge.
In case you weren't aware, there are several web-based status reporting tools
available which can provide you, the maintainer, with an overview of your
packages. Briefly, these are: