>> Good practice is to backport just after you commit on
>> trunk/py3k, not months later.
>
> Obviously, but people forget or simply choose not to.
I'd say: "tough luck, then". If people don't port a fix in some
branch, the bug stays unfixed in that branch. So what: if somebody
runs into the bug
On Fri, Jul 2, 2010 at 01:57, Antoine Pitrou wrote:
>
>> > - I will initialize svnmerge from py3k -> 2.7maint.
>>
>> We should probably all get into the habit of making sure that we leave
>> any issues open with Python 2.7 flagged as an effected version to get
>> fixes ported. These then could bec
On Fri, Jul 2, 2010 at 11:02, Georg Brandl wrote:
> While that would be logical if we continued to use SVN, it's probably not
> worth it when we switch to Hg anyway a short time later, so avoiding the
> potential confusion is better.
Agreed, renaming the branch has the potential of making the con
Am 02.07.2010 09:53, schrieb M.-A. Lemburg:
> M.-A. Lemburg wrote:
>> Benjamin Peterson wrote:
>>> After I tag 2.7 this Saturday, I will effect the following changes in
>>> the repository:
>>> - I will make the 2.7 maintenance branch.
>>> - I will remove svnmerge from trunk -> py3k.
>>> - I will in
> > - I will initialize svnmerge from py3k -> 2.7maint.
>
> We should probably all get into the habit of making sure that we leave
> any issues open with Python 2.7 flagged as an effected version to get
> fixes ported. These then could become "easy" issues for people to
> contribute through by le
M.-A. Lemburg wrote:
> Benjamin Peterson wrote:
>> After I tag 2.7 this Saturday, I will effect the following changes in
>> the repository:
>> - I will make the 2.7 maintenance branch.
>> - I will remove svnmerge from trunk -> py3k.
>> - I will initialize svnmerge from py3k -> 2.7maint.
>> - The tr
Benjamin Peterson wrote:
> After I tag 2.7 this Saturday, I will effect the following changes in
> the repository:
> - I will make the 2.7 maintenance branch.
> - I will remove svnmerge from trunk -> py3k.
> - I will initialize svnmerge from py3k -> 2.7maint.
> - The trunk will be officially closed
On Thu, Jul 1, 2010 at 20:17, Benjamin Peterson wrote:
> After I tag 2.7 this Saturday, I will effect the following changes in
> the repository:
> - I will make the 2.7 maintenance branch.
> - I will remove svnmerge from trunk -> py3k.
Thanks for going through to make sure no commits were going t
After I tag 2.7 this Saturday, I will effect the following changes in
the repository:
- I will make the 2.7 maintenance branch.
- I will remove svnmerge from trunk -> py3k.
- I will initialize svnmerge from py3k -> 2.7maint.
- The trunk will be officially closed. I suggest you just delete your
trun
