On Sun, Jul 01, 2012 at 03:58:45AM +0200, Leo 'costela' Antunes wrote: > Hi, > > Hope you guys don't mind if I just jump in here and try to cool down the > discussion, since it's getting kinda "flamy".
Yeah, that tends to happen when people get tired of repeating themselves to Goswin, and he keeping wanting to harp on about it ... This already got resolved on IRC, and I only replied here to make it clear to anyone looking at the bug that this really was off the table for Wheezy now. The discussion can't really get much cooler than "Wheezy is now frozen". > To get some distance and perspective I'd suggest referring this to the > release-team: if they see the possible downfall as an acceptable > trade-off for the multi-arch release goal, then go ahead with the > patching, uploading and fixing bugs as they appear. Otherwise leave it be. So let's not annoy them with this now please. The only possible outcome of doing this now for them is "more pain and more work and more delays before we are in a state to release". It will make it impossible for them to binNMU this package should it need it, and it will burn up their time needing to review patches that really aren't fixing anything that is remotely release critical. And they already have enough people requesting crazy freeze exceptions from them ... If nobody noticed they needed an m-a version of this before now, then clearly it's not a high priority for them, and it can easily wait until there is a better time to start experimenting with this again. The sooner the remaining RC bugs are fixed and we release, the sooner that will happen. This is how release cycles work. It's too late for untested things now. But thanks for the good intentions, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
