keeping track of regressions during the development cycle

Matt Zimmerman mdz at ubuntu.com
Tue Jul 22 18:38:17 BST 2008


On Thu, Jul 17, 2008 at 11:21:51AM +0100, Steve Langasek wrote:
> From time to time in the course of a development cycle, it's necessary to
> make changes of a temporary nature that should be revisited and (hopefully)
> reverted before the final release.  In order for the project as a whole to
> be better able to track such changes, it would be a good idea to have a
> consistent policy for how these bugs will be represented in Launchpad.
> 
> The proposed policy is that these bugs should be tracked as release-critical
> bugs: nominated for the release, and targeted to the milestone before which
> the change needs to be reviewed.  This policy has been documented on
> <https://wiki.ubuntu.com/UbuntuDevelopment> and on
> <https://wiki.ubuntu.com/RCBugTargetting>.
> 
> As usual, please send any feedback to ubuntu-devel / ubuntu-devel-discuss.

What about regressions which aren't introduced intentionally?  I think we
should have a standard way of keeping track of those (even if it's as simple
as a tag), and a process by which we decide which ones should become
release targets.

-- 
 - mdz



More information about the ubuntu-devel mailing list