Package: release.debian.org Severity: wishlist I brought this up in Cambridge, filing here so we can discuss specifics.
At Mozilla we're using a template in bugzilla [1] for requests to cherry-pick changes from trunk to a release branch, to help release management assess reward/risk from specific changes, and I thought something like that might be useful in Debian too. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1320338 [Feature/Bug causing the regression]: [User impact if declined]: [Is this code covered by automated tests?] [Has the fix been verified in Nightly?] [Needs manual test from QE? If yes, steps to reproduce]: [List of other uplifts needed for the feature/fix]: [Is the change risky?]: [Why is the change risky/not risky?]: [String changes made/needed]: I think most of it would also be useful here, framed something like: - when was the bug introduced, is it a regression - user impact of the bug - what automated or manual tests cover the affected code - has the change been verified in sid - some discussion of the risks involved, if only so the maintainer/submitter asks themselves that question - l10n impact It can't be too long or it will be a pain for people to write and for us to read, so maybe we should trim that down a bit, but if we can reduce the back and forth by having more relevant information in those bug reports I think that might be useful. Ubuntu may have something in their SRU bug process too? Eventually we could reassign this to reportbug if/when we come to an agreement. Cheers, Julien
