-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 17, 2008, at 11:35 PM, Guido van Rossum wrote:
> What do I do for something that should absolutely go into the 2.6final > release (say) but is otherwise pretty minor? I've been using critical > to make sure it doesn't get put off until past the release. Critical is the right one to use. Neal and I will basically be moving issues between 'release blocker' and 'critical' with the former meaning this issue blocks the upcoming release. The latter means it will (probably) block an upcoming release. I think when we make a major milestone, e.g. the first beta, the first release candidate, etc., we'll triage those critical and move some up to release blockers. We should not release the finals until there are no release blockers or criticals. Either the critical gets moved to high and ignored, or it gets moved to release blocker and gets fixed. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR99JvnEjvBPtnXfVAQJwuwQAh5mhXdwg7t9FAsNXJ69OoPM6qj37OjP4 +3SjZMn9A1qObFB7biUV6P47KwydzDskMaswifMv9eV94+ccb0mIlDC/SgdjB9h8 JtuJq6mZ1nIUqQSLtX4W6op4G/Zpk/cerrbBzTWt06VU8yi7XhoBCVjDDVn37Nwv Kh260/8ewnw= =dMJV -----END PGP SIGNATURE----- _______________________________________________ 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
