On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:
In article <11a6545d-7204-4f61-b55b-1cc77cb56...@python.org>, Barry Warsaw <ba...@python.org> wrote:I still want to release by the 25th, but I'd be willing to move the rcto Monday the 21st. We're really just trying to avoid a brown bagmoment, so that should give us enough time to double check the releases.The recent release of OS X 10.6 (Snow Leopard) has triggered a fairamount of 2.6 bug tracker activity, since 10.6 now includes 2.6 (2.6.1)and a 64-bit version at that. A number of patches have either just been checked-in over the past couple of weeks or are getting some exposure before check-in. Given the timing and the (appropriate) infrequency of 2.6.x releases, I think it would be unfortunate to push 2.6.3 out the door without ensuring that it works well on 10.6. Therefore, I propose that 2.6.3 should have 10.6 compatibility as a "release goal".Without trying to put Ronald on the spot (too much!), it would be a goodidea to get his assessment where things stand wrt 2.6 on 10.6 before setting a final release date.
I'm hoping that Python won't have any issues building and running on 10.6, but I don't have it yet so I can't personally test it out.
How would you quantify "works well"? Do you have any thoughts on tests you'd run other than the standard test suite? If 2.6.3 is shown to pass its test suite on 10.5.x, is that good enough? Are the specific bug fixes necessary for 10.6?
-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
