On Thu, Feb 07, 2013 at 11:08:55AM +0100, Daniel Baumann wrote: > i'm argueing for either an explicit unfrozen sid or an explicit > frozen sid. since it's neither right now, and you intend to > overwrite the maintainers decision via CTTE to upload newer syslinux > to sid, you need to argue against it, not 'doesn't gain anything'. Daniel, I don't think this is the place for such a broad discussion. I believe we would all agree that a frozen distro development (no matter the suite where it happens) is a PITA that we could all live without. But at present, this is what our release processes and technologies offer. Like it or not. It would be very nice to improve them, and I've high hopes that dak based personal package archives would help a lot with that, but this is not the time for this kind of changes. More importantly, it is arguably false that sid is not "explicitly frozen". The freeze policy [1], which has been repeatedly announced on d-d-a, reads: > Please also note that since many updates (hopefully, the vast > majority) will still be going in through unstable, major changes in > unstable right now can disrupt efforts to get RC bugs fixed. We don't > ask you not to make changes in unstable, but we do ask that you be > aware of the effects your changes can have -- especially if you > maintain a library. Please continue to keep disruptive changes out of > unstable and continue making use of experimental where > appropriate. Note that you can stage NEW uploads in experimental to > avoid disruption in unstable. [1]: http://release.debian.org/wheezy/freeze_policy.html by evidence, your change to unstable has been disruptive. I understand (better, I trust your claim on that, but I haven't checked) that experimental is not a viable path for syslinux development. But that is no justification for getting in the way of a release, going explicitly against the freeze policy. Please put back in sid the syslinux version that the release team wants to see in there. Ideally, it wouldn't be for long, and an action of that kind will avoid burning cycles of all the people participating in this thread. I'm pretty sure we can all use those cycles to the betterment of Wheezy instead. As soon as Wheezy is out of the door, please re-raise this topic in a project-wide place, where we can work on solutions to avoid this kind of frustrating long freezes. That would be the appropriate time and place for this kind of discussions. Cheers. -- Stefano Zacchiroli . . . . . . . zack@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
Attachment:
signature.asc
Description: Digital signature