[Python-Dev] Change in priority fields

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 18, 2008, at 12:11 AM, Guido van Rossum wrote:

> Hm... This feels a bit like inflation of priorities to me; there would
> be lots of critical bugs and quite a few release blockers... The
> highest priority just pertains to the upcoming release which could be
> weeks in the future.

I want a very simple roundup query that I can consult during the  
release cycle to know whether everything's fine, or whether I have to  
start pestering people and pull the big red "STOP RELEASE" button.   
Critical gives us a priority for things we really need to fix, but  
maybe not right this second.

> I'd be more comfortable if there were 1-2
> priorities above that, e.g. one higher for stuff that makes a buildbot
> go red (i.e. breaks a test) and two higher for stuff that affects most
> developers (e.g. stuff checked in that doesn't even build).

I think neither of these use cases should get that far.  Neal and I  
talked it over and we're in agreement that if a commit makes the  
buildbots go red or breaks the build, we're going to just revert it.   
Tough luck Joe Dev, please test your changes more carefully next time.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iQCVAwUBR9/GJHEjvBPtnXfVAQJEugQAnyPR4WkSW7R2QN4F6v1zgQakD/8yVxCn
TMESNJaG1XHhZJlZ6gSl5SBmy5PFS0w4GeUayXjbxFbH/hdpNWfAeWwgY+5+W/6S
A3JO96nz89JUXqiRvOab7QaDl8N1KSd0Om7rJo50XKZZqJBNO6/ypL9mr1nAvUp/
ppZ614lz15I=
=HCH0
-----END PGP SIGNATURE-----