Re: RC severity for Python 2.6 related bugs
On Sun, Feb 28, 2010 at 04:46:09PM +0100, Josselin Mouette wrote:
> Le dimanche 28 février 2010 à 15:29 +0100, Vincent Bernat a écrit :
> > It would be far easier to let Python 2.6 be the default, then file (or
> > upgrade) serious bugs and solve them in a week or two.
>
> Yeah sure, let’s knowingly break dozens of packages by switching instead
> of fixing them before and make it painless for users.
I think we need to do both before we end up running out of time. I
propose that we upgrade/file bugs as serious so that they get maintainer
attention where possible, and allow (let's say) 7 days to react.
After this time, Python 2.6 should become default in sid and all such bugs
are NMU candidates. If nothing else gets maintainer's attention, this will.
--
Jonathan Wiltshire
1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: