[Python-Dev] 2.6 and 3.0 project management

Barry Warsaw barry at python.org
Mon Mar 17 00:46:50 CET 2008

Hash: SHA1

On Mar 16, 2008, at 3:56 PM, Guido van Rossum wrote:

> On Sun, Mar 16, 2008 at 12:24 PM, Barry Warsaw <barry at python.org>  
> wrote:
>> I mentioned this to Guido and got a positive response, so let me  
>> state
>> my preference for your feedback.  I plan on holding up the final
>> releases until both versions are ready to go.  I think this will help
>> motivate us to give Python 2.6 the love it needs if it's lagging
>> behind 3.0, and I completely agree with Guido that this let's our
>> community know that both versions are equally important to us.
> It's a deal.


>> The other thing is that I'd really like is a "show stoppers" Roundup
>> search.  The idea is that if our core buildbots look good and the
>> "show stoppers" search turns up no items, then I know I can cut a
>> release (at least for alphas, betas, and rcs).  If there are "show
>> stoppers" then I have something that I can triage (and maybe re- 
>> assign
>> severity) or start publicly harassing people into fixing.
> How about using the "critical" Severity for show stoppers?

'critical' is fine (or 'immediate').  My problem before was that I  
couldn't do one query that gave me all the critical issues for both  
2.6 and 3.0.  That certainly could have been pebkac though.  Neal  
mentioned that that kind of query should be possible, if it's not  
already there.

- -Barry

Version: GnuPG v1.4.8 (Darwin)


More information about the Python-Dev mailing list