On Tue, May 28, 2013 at 4:56 PM, Terry Reedy wrote:
> On 5/28/2013 7:23 PM, Guido van Rossum wrote:
>
>> On Tue, May 28, 2013 at 3:00 PM, Terry Reedy wrote:
>>
>>> As I said on the issue and in response to Benjamin's question, I prefer
>>> to
>>> have it appear near the top of the directory list
Is there a merge pending from 3.2 to 3.3?
http://hg.python.org/cpython/graph/83973?revcount=240 shows that last 3.2
change occurred 10 days ago and the branch has not been merged into 3.3 yet.
http://hg.python.org/cpython/rev/b9b521efeba3?revcount=240
Is it pending intentionally or this should b
On Wed, 29 May 2013 06:11:51 -0700, Senthil Kumaran wrote:
> Is there a merge pending from 3.2 to 3.3?
>
> http://hg.python.org/cpython/graph/83973?revcount=240 shows that last 3.2
> change occurred 10 days ago and the branch has not been merged into 3.3 yet.
>
> http://hg.python.org/cpython/rev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/05/13 16:41, R. David Murray wrote:
> I asked about this on IRC and was told that 3.2 is now a
> standalone branch like 2.7. Security fixes will be applied by the
> release manager only, and Georg doesn't see any point in null
> merging the comm
On Wed, 29 May 2013 21:41:58 +0200, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 29/05/13 16:41, R. David Murray wrote:
> > I asked about this on IRC and was told that 3.2 is now a
> > standalone branch like 2.7. Security fixes will be applied by the
> > release mana
On Wed, May 29, 2013 at 7:41 AM, R. David Murray wrote:
>
> I asked about this on IRC and was told that 3.2 is now a standalone branch
> like 2.7. Security fixes will be applied by the release manager only,
> and Georg doesn't see any point in null merging the commits.
>
>
Well, there is no harm
On May 29, 2013, at 03:53 PM, R. David Murray wrote:
>By making it a release blocker in the tracker. (Once it is
>public...I would imagine release managers have to be on the
>security mailing list...though I don't know that for a fact.)
Yes, all release managers for active branches are on the se
