Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
(Nearly) full tickless operation in 3.10
Other desktop support?
Posted Jan 16, 2013 18:56 UTC (Wed) by vonbrand (subscriber, #4458)
Because if they only froze testing, all its users would migrate to unstable...
Posted Jan 17, 2013 7:57 UTC (Thu) by DavidS (subscriber, #84675)
Because "unstable" is the place where stuff goes that should be released with the next stable. See Developer Reference 18.104.22.168:
> This development cycle is based on the assumption that the unstable
> distribution becomes stable after passing a period of being in testing.
Posted Jan 17, 2013 8:05 UTC (Thu) by micka (subscriber, #38720)
Posted Jan 18, 2013 6:30 UTC (Fri) by DavidS (subscriber, #84675)
Uploading to unstable publishes packages as "destined for stable". In the case of libraries, that also means that users of this library will start linking against the new binary. This again implies that the two packages now must go to testing together. This quickly leads to situations where significant parts of unstable cannot progress to testing due to issues in central packages (think gtk).
Building new packages against libraries from testing would reduce the formal requirements for testing propagation, but would lead to untested combinations in testing (as unstable users had a different version installed).
Posted Jan 18, 2013 8:06 UTC (Fri) by micka (subscriber, #38720)
> Building new packages against libraries from testing would reduce the formal requirements for testing propagation, but would lead to untested combinations in testing
But I'd prefer that. I still think that those who care about testing should be the ones testing it.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds