<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 22/07/11 11:07, John Arbash Meinel wrote: <blockquote cite="mid:4E293DED.20708@arbash-meinel.com" type="cite"> <pre wrap="">On 7/22/2011 10:48 AM, vila wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, I just finished adding <a class="moz-txt-link-freetext" href="http://babune.ladeuil.net:24842/view/SRUs/job/selftest-chroot-natty-proposed/">http://babune.ladeuil.net:24842/view/SRUs/job/selftest-chroot-natty-proposed/</a> This job installs bzr from natty-proposed and run the full test suite for the installed bzr. This will be run every 24h from now (and be extended to other series). Vincent </pre> </blockquote> <pre wrap=""> I like that we're running the test suite, but it doesn't feel quite right. My thoughts: 1) Aren't we running the test suite as part of building the package? So any given revision in natty-proposed has *already* passed the test suite on natty.</pre> </blockquote> Yep. <blockquote cite="mid:4E293DED.20708@arbash-meinel.com" type="cite"> <pre wrap="">2) Development isn't being done in a "-proposed" branch. AIUI, it shouldn't get into the -proposed branch until we've released a stable version. Which means the testing should be done on our stable branches (which I think you're already doing). Anyway, I'm not against doing it, but I don't really see what benefit we get out of it, either. </pre> </blockquote> The SRU process ( <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <a href="https://wiki.ubuntu.com/StableReleaseUpdates">https://wiki.ubuntu.com/StableReleaseUpdates</a>) requires that proposed packages (and the bugs they fix) are verified. Usually this happens by manually checking that each backported bugfix has not broken anything. For Bazaar, we are allowed to verify that the built packages are not broken by running the testsuite from the installed package on the target distroseries. Running the test suite from the package might catch some issues like incomplete installation. In the past we've forgotten to install some of our packages, resulting in a broken bzr when installed, when it ran fine from the source tree. Likewise, we have had bugs in the packaging that caused files to be installed in the wrong location. Cheers, Jelmer </body> </html>