Re: [python-committers] Cutting Python 2.6

2008-10-02 Thread Nicholas Bastin
On Thu, Oct 2, 2008 at 3:55 PM, "Martin v. Löwis" <[EMAIL PROTECTED]>wrote: > > Suppose you have three subsequent revisions in the trunk: > > A contains what you originally wanted to tag > A+1 contains a change by somebody else, not to be released > A+2 is the change that you made to fix a bug you

Re: [python-committers] Cutting Python 2.6

2008-10-02 Thread Nicholas Bastin
On Thu, Oct 2, 2008 at 4:25 PM, "Martin v. Löwis" <[EMAIL PROTECTED]>wrote: > > You always create a branch for the release (subversion doesn't make any > > distinction between a tag and a branch anyhow, so you might as well just > > make a branch). > > I don't think the tag should be edited (there

Re: [python-committers] Cutting Python 2.6

2008-10-02 Thread Nicholas Bastin
On Thu, Oct 2, 2008 at 5:08 PM, Fredrik Lundh <[EMAIL PROTECTED]>wrote: > > How do you create the release tag so that it contains change > > sets A and A+2, but not A+1? (and no, creating a branch just for > > the release is no option, because that means you have to copy all > > the changes you ma