I'm not necessarily saying these shouldn't go into 2.6.5, but this late in the
release cycle, every change needs to be justified. My preferred way of doing
so is by filing a release blocker issue stating and backing up the requested
change. We can then discuss any potential impact on release t
Am 13.03.2010 17:51, schrieb Barry Warsaw:
> I'm not necessarily saying these shouldn't go into 2.6.5, but this late in
> the release cycle, every change needs to be justified. My preferred way of
> doing so is by filing a release blocker issue stating and backing up the
> requested change. We ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2010 05:42 PM, Barry Warsaw wrote:
> All: The release26-maint branch is now semi-thawed. I'm going to be even more
> strict about commits to the branch now because I really don't want to release
> an rc3 unless absolutely necessary. 2.6.5 fi
Le Sat, 13 Mar 2010 20:42:33 +0100,
Jesus Cea a écrit :
>
> I was wondering about http://bugs.python.org/issue3928 . It is a
> trivial fix a couple of lines long only.
We have lots of "trivial" fixes in the tracker, though.
___
python-committers maili
Antoine Pitrou wrote:
> Le Sat, 13 Mar 2010 20:42:33 +0100,
> Jesus Cea a écrit :
>> I was wondering about http://bugs.python.org/issue3928 . It is a
>> trivial fix a couple of lines long only.
>
> We have lots of "trivial" fixes in the tracker, though.
It's not a regression from 2.6.4, so it's
On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote:
>I was wondering about http://bugs.python.org/issue3928 . It is a trivial
>fix a couple of lines long only.
These can be addressed for 2.6.6.
-Barry
signature.asc
Description: PGP signature
___
python-co
On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote:
>No need to file a new issue -- I've promoted 8111 to release blocker.
>I've added an explanation and a collective diff. No further RC is needed.
Thanks; I've accepted and closed the issue.
>Sorry for directly committing this, but I felt it was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2010 11:25 PM, Barry Warsaw wrote:
> On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote:
>
>> I was wondering about http://bugs.python.org/issue3928 . It is a trivial
>> fix a couple of lines long only.
>
> These can be addressed for 2.6.6.
Your
2010/3/13 Jesus Cea :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/13/2010 11:25 PM, Barry Warsaw wrote:
>> On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote:
>>
>>> I was wondering about http://bugs.python.org/issue3928 . It is a trivial
>>> fix a couple of lines long only.
>>
>> These
Le Sat, 13 Mar 2010 17:19:39 -0600,
Benjamin Peterson a écrit :
> >
> > What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
> > since the rc is out. I saw your message asking for stopping commits
> > the 6th march, but I haven't seen another message opening the gates
> > again...
>
> A
Am 14.03.2010 00:08, schrieb Barry Warsaw:
> On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote:
>
>>No need to file a new issue -- I've promoted 8111 to release blocker.
>>I've added an explanation and a collective diff. No further RC is needed.
>
> Thanks; I've accepted and closed the issue.
>
>>> What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
>>> since the rc is out. I saw your message asking for stopping commits
>>> the 6th march, but I haven't seen another message opening the gates
>>> again...
>> As Martin pointed out, I don't think this patch is acceptable for a
>> b
2010/3/13 "Martin v. Löwis" :
What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
since the rc is out. I saw your message asking for stopping commits
the 6th march, but I haven't seen another message opening the gates
again...
>>> As Martin pointed out, I don't think
Am 14.03.2010 00:35, schrieb Georg Brandl:
> Am 14.03.2010 00:08, schrieb Barry Warsaw:
>> On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote:
>>
>>>No need to file a new issue -- I've promoted 8111 to release blocker.
>>>I've added an explanation and a collective diff. No further RC is needed.
>>
> Thinking of that a bit more: after the Hg transition, shouldn't we be able to
> really freeze a branch that is in pre-release approval-needed mode? It is
> trivial for anyone to commit a fix to their own branch, and then instead of
> pushing they'd have to notify the release manager to pull from
Am 14.03.2010 00:53, schrieb "Martin v. Löwis":
>> Thinking of that a bit more: after the Hg transition, shouldn't we be able to
>> really freeze a branch that is in pre-release approval-needed mode? It is
>> trivial for anyone to commit a fix to their own branch, and then instead of
>> pushing th
Le Sun, 14 Mar 2010 01:03:00 +0100,
Georg Brandl a écrit :
>
> > As for pulling from committer branches: that would require that
> > committers host their branches somewhere.
>
> Yes. But that's no big deal, isn't it? They can use a public hg
> hoster like bitbucket, or we can have a facility
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2010 12:40 AM, Benjamin Peterson wrote:
> 2010/3/13 "Martin v. Löwis" :
> What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
> since the rc is out. I saw your message asking for stopping commits
> the 6th march, but I h
2010/3/13 Jesus Cea :
> I will commit the patch to trunk and py3k, and to 2.6 and 3.1 branch
> after 2.6.5 and 3.1.2 are out.
>
> Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do
> the four commits at the same time?. Don't want to miss the 2.7beta.
That's up to you.
>
> Mercu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2010 03:35 AM, Benjamin Peterson wrote:
>> Mercurial, where are you?. This would be a non issue :)
>
> How so?
The release manager could clone the repository to getting it ready for
release, while the main repository accepts new changesets.
20 matches
Mail list logo
