On Tuesday, December 02, 2014 04:54:37 PM Donald Stufft wrote: > > On Dec 2, 2014, at 4:47 PM, Scott Kitterman <deb...@kitterman.com> wrote: > > > > On Tuesday, December 02, 2014 04:15:05 PM Donald Stufft wrote: > > ... > > > >> I have another question. If we fix this in the upcoming pip 6 release > >> what > >> is the chances of getting an exception for pip 6 in the freeze? If I can > >> solve the problem in pip proper and keep the delta between different > >> platforms smaller I can juggle around priorities and push the other big > >> ticket thing I was working on till another release. > > > > ... > > The deadline for getting Important (i.e. not Serious/Grave/Critical) bug > > fixes unblocked for Jessie is December 5th (that's uploaded to Debian and > > the release team has reviewed and unblocked it). > > > > Unless the next release is ~nothing but fixes for important/release > > critical bugs, the chance is approximately zero. > > > > Scott K > > This bug is marked “Serious” right? So if I understand correctly a new > version isn’t acceptable, even to fix a Serious issue, unless it only fixes > items that are allowed within whatever phase the release process is in?
A new release would be acceptable if it only fixed release critical stuff. The problem comes in where a new release fixes something serious and other stuff. Scott K _______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
