Re: Automated piuparts when entering the archive (Was: Debian development and release: always releasable (essay))
On Tue, May 21, 2013 at 01:21:41AM +0200, Andreas Beckmann wrote:
> That might be possible with DPAs and if upload management is changed
> generally to get less "broken" packages into unstable. E.g.
I think that most of the ideas you presented are very useful and other
responses have (silently) expressed this as well. What is not so clear
is how to get there. Of course all the testing features you mentioned is
not a thing to just switch it on, but there will be a gradual
transition.
Could you (or anyone else) give a rough idea of what work needs to be
done to get there? And in which order? I mean getting just a subset of
what you mentioned (e.g. FTBFS testing or any piuparts run or
autopkgtest) would be beneficial by itself.
As far as I can see there are a few roughly independent aspects here:
* dynamic addition of new suites to the archive
* buildd support for Architecture:all
* infrastructure that regularly runs autpkgtest
* extend the existing piuparts infrastructure to handle more load
* some work on britney?
This list is incomplete, probably wrong and not very precise.
Helmut
Reply to: