micro release exception for bzr
Kees Cook
kees.cook at canonical.com
Tue Sep 21 15:17:03 BST 2010
On Fri, Sep 17, 2010 at 11:14:58AM +0100, Colin Watson wrote:
> On Fri, Sep 17, 2010 at 09:56:02AM +0100, Mark Shuttleworth wrote:
> > On 17/09/10 08:19, Martin Pool wrote:
> > > We have a pretty substantial test suite (about 26,000 tests) which is
> > > run on every release-branch commit, and we require new tests for bug
> > > fixes or features if it is at all practical. I believe the tests are
> > > currently done during upstream releases rather than during package
> > > builds, but I see no reason why they couldn't be turned on there.
> >
> > I'd rather require a manual test run confirmation before the archive
> > pocket copy from -proposed to -updates than hammer the buildds every
> > single time we build bzr.
>
> IMO, we should generally be running test suites by default on package
> uploads unless there's a very good reason not to; this is even part of
> our main inclusion guidelines.
I feel similarly. Having the tests on is just another place to avoid manual
testing.
However, given the history of bzr SRUs, I'm fine to approve this for MRE.
-Kees
--
Kees Cook
Ubuntu Security Team
More information about the technical-board
mailing list