Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Georg Brandl
Am 02.02.2011 19:47, schrieb Antoine Pitrou: > Le mercredi 02 février 2011 à 19:39 +0100, Jesus Cea a écrit : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 02/02/11 19:28, Antoine Pitrou wrote: >> >> The merge here is mostly automatic. In fact, if the RM doesn't change >> >> his/her

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Georg Brandl
Am 03.02.2011 01:37, schrieb Jesus Cea: > On 02/02/11 21:30, Barry Warsaw wrote: >>> Just exactly the reverse of current workflow. > >> And for good reason (IMO). It's often much less clear exactly how far back a >> specific patch should be committed when it's first being developed. It makes >>

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Nick Coghlan
On Thu, Feb 3, 2011 at 10:37 AM, Jesus Cea wrote: > In fact, "up-porting" is usually better, because you don't have to think > if you must downport or not. Versión "n+1" is always a superset of > versión "n". So you "up-port" *ALWAYS*, automatically (mostly) via merge. As I said, I'm happy to rol

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Antoine Pitrou
Le jeudi 03 février 2011 à 22:04 +1000, Nick Coghlan a écrit : > On Thu, Feb 3, 2011 at 10:37 AM, Jesus Cea wrote: > > In fact, "up-porting" is usually better, because you don't have to think > > if you must downport or not. Versión "n+1" is always a superset of > > versión "n". So you "up-port" *

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Nick Coghlan
On Thu, Feb 3, 2011 at 10:20 PM, Antoine Pitrou wrote: > Le jeudi 03 février 2011 à 22:04 +1000, Nick Coghlan a écrit : >> On Thu, Feb 3, 2011 at 10:37 AM, Jesus Cea wrote: >> > In fact, "up-porting" is usually better, because you don't have to think >> > if you must downport or not. Versión "n+1

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Barry Warsaw
On Feb 03, 2011, at 09:01 AM, Georg Brandl wrote: >I don't think branching off at beta1 is helpful. Developers will happily >continue adding features to trunk (because that's what's fun, isn't it), >and not care much about the release branch. Obviously we want the opposite, >and we want them to

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Barry Warsaw
On Feb 03, 2011, at 08:58 AM, Georg Brandl wrote: >Exactly. This is why I didn't do it that way it during the 3.2 releases; I >was always waiting for the hg switch to happen, and until then I thought it >best not to change the process. Smart man. :) We have a perfect storm approaching for the m

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Antoine Pitrou
Le jeudi 03 février 2011 à 09:01 +0100, Georg Brandl a écrit : > I don't think branching off at beta1 is helpful. Developers will happily > continue adding features to trunk (because that's what's fun, isn't it), > and not care much about the release branch. Obviously we want the opposite, > and

Re: [python-committers] hg migration

2011-02-03 Thread Antoine Pitrou
Le jeudi 03 février 2011 à 16:36 -0500, Barry Warsaw a écrit : > On Feb 03, 2011, at 08:58 AM, Georg Brandl wrote: > > >Exactly. This is why I didn't do it that way it during the 3.2 releases; I > >was always waiting for the hg switch to happen, and until then I thought it > >best not to change t

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Georg Brandl
Am 03.02.2011 22:39, schrieb Antoine Pitrou: > Le jeudi 03 février 2011 à 09:01 +0100, Georg Brandl a écrit : >> I don't think branching off at beta1 is helpful. Developers will happily >> continue adding features to trunk (because that's what's fun, isn't it), >> and not care much about the relea

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Georg Brandl
Am 03.02.2011 22:36, schrieb Barry Warsaw: > On Feb 03, 2011, at 08:58 AM, Georg Brandl wrote: > >>Exactly. This is why I didn't do it that way it during the 3.2 releases; I >>was always waiting for the hg switch to happen, and until then I thought it >>best not to change the process. > > Smart

Re: [python-committers] hg migration

2011-02-03 Thread Barry Warsaw
On Feb 03, 2011, at 10:40 PM, Antoine Pitrou wrote: >I'm not sure all of us will be *physically* in Atlanta - although >there's no doubt we'll think about you :) I guess that means you won't be there? Bummer! -Barry signature.asc Description: PGP signature

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Barry Warsaw
On Feb 03, 2011, at 10:54 PM, Georg Brandl wrote: >I'm still hoping to get the conversion done *before* PyCon, so that everyone >can already get familiar with the new system, in order to be productive at the >sprints. But of course, I'm also counting on PyCon sprints as the "last line >of defence

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/11 13:04, Nick Coghlan wrote: > On Thu, Feb 3, 2011 at 10:37 AM, Jesus Cea wrote: >> In fact, "up-porting" is usually better, because you don't have to think >> if you must downport or not. Versión "n+1" is always a superset of >> versión "n"

Re: [python-committers] [PSF-Members] Code Simplicity » Open Source Community, Simplified

2011-02-03 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/02/11 15:07, Nick Coghlan wrote: > One useful thing I have personally gotten out of this discussion is to > identify the core reason I feel backporting is the "right" way to > handle maintenance branches: it ensures that the *tests* that confirm