Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-05 Thread Georg Brandl
Christian Heimes schrieb: Georg Brandl schrieb: David Goodger schrieb: On Thu, Jul 2, 2009 at 14:56, R. David Murrayrdmur...@bitdance.com wrote: I can see it now...the TV and movie track at PyCon 2010, with attendance mandatory for anyone wanting to participate in the Core sprint... We

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-04 Thread Antoine Pitrou
Le jeudi 02 juillet 2009 à 11:43 -0700, Brett Cannon a écrit : Considering Georg just discovered Fawlty Towers I think we might need to have required British humour training for all core committers. I object to the British humour monopoly. I know as a fact that Georg likes French humour a lot

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-03 Thread Georg Brandl
David Goodger schrieb: On Thu, Jul 2, 2009 at 14:56, R. David Murrayrdmur...@bitdance.com wrote: I can see it now...the TV and movie track at PyCon 2010, with attendance mandatory for anyone wanting to participate in the Core sprint... We actually had a room or two for evening videos at a

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-03 Thread Christian Heimes
Georg Brandl schrieb: David Goodger schrieb: On Thu, Jul 2, 2009 at 14:56, R. David Murrayrdmur...@bitdance.com wrote: I can see it now...the TV and movie track at PyCon 2010, with attendance mandatory for anyone wanting to participate in the Core sprint... We actually had a room or two for

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anthony Baxter wrote: Speaking as a past release manager, the reason that things like that didn't get merged is because... drumroll... no-one merged them. Ughhh. This is actually a good reason to migrate to mercurial, were merges are painless :-).

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Benjamin Peterson
2009/7/2 Jeroen Ruigrok van der Werven asmo...@in-nomine.org: -On [20090702 17:15], Jesus Cea (j...@jcea.es) wrote: Ughhh. This is actually a good reason to migrate to mercurial, were merges are painless :-). For all I know Mercurial doesn't make the issue of resolving content merges easier,

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Peterson wrote: 2009/7/2 Jeroen Ruigrok van der Werven asmo...@in-nomine.org: -On [20090702 17:15], Jesus Cea (j...@jcea.es) wrote: Ughhh. This is actually a good reason to migrate to mercurial, were merges are painless :-). For all I

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Brett Cannon
2009/7/2 Anthony Baxter anthonybax...@gmail.com The particulars of the revision control system don't matter as much as the discipline of teaching people to commit fixes. Right now, we have 2.6.x, 3.0.x and 3.1.x. If I remember correctly I believe we decided at the language summit that 3.0 is

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Barry Warsaw
On Jul 2, 2009, at 1:56 PM, Brett Cannon wrote: If I remember correctly I believe we decided at the language summit that 3.0 is just dead now that 3.1 is out and we shouldn't even bother with another point release since 3.1 followed 3.0 so closely and didn't introduce any new syntax or

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Barry Warsaw
On Jul 2, 2009, at 4:09 PM, Brett Cannon wrote: If Barry is up for it I am not against it, but if we do go with it I think it should be a quickie release and then retire 3.0.x completely. It's not difficult to actually cut the release. What is a pain is managing all the bugs leading up to

Re: [python-committers] Why r69846 is not merged to release26-maint?

2009-07-02 Thread Steve Holden
Brett Cannon wrote: On Thu, Jul 2, 2009 at 11:42, Barry Warsaw ba...@python.org mailto:ba...@python.org wrote: On Jul 2, 2009, at 2:29 PM, Anthony Baxter wrote: I think Barry should totally cut a completely pointless 3.0.2 release. We can call it the