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 therewere any fixes _at all_ that there would be a new rc. Only when nobugs 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
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
