On Oct 13, 2009, at 6:10 PM, Martin v. Löwis wrote: >> I always thought that the idea of a release candidate was that if >> there >> were any fixes _at all_ that there would be a new rc. Only when no >> bugs needing fixed are found does the rc turn into the actual >> release. > > This was also my understanding; that's the point of calling it > "candidate". Since the code base of 2.6.4rc1 was not released as-is, > we would need to consider another candidate. > > But then, Barry doesn't like release candidates in the first place. No, but let's do one anyway! So, we can either make Sunday's release rc2 and do the final release one week later, or I can try to get an rc2 out in the next day or two, with a final release mid-next week. Thoughts? -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 832 bytes Desc: This is a digitally signed message part URL: <http://mail.python.org/pipermail/python-dev/attachments/20091013/7027cbcd/attachment.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4