micro release exception for bzr

[Martin Pitt]

Matt Zimmerman [2010-12-15 11:11 +0000]:
> Works for me.  The important thing is that we have assurance that the tests
> pass on the build we're going to ship to users.  Running the tests during
> the build is just the simplest way to manage that assurance, but if it can
> be provided by other means, that should be sufficient.

It doesn't prevent e. g.  forgetting to actually install new files
from a new version in debian/*.install, putting them into the wrong
destination path, or a problem with the python integration. So for SRU
verification I'm actually more interested in testing the actually
installed .deb.

That said, test suites during build are helpful as well, as they
catch regressions early and thus prevent getting the regressing
package to users.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)