On 07/03/07, Alan Conway <[EMAIL PROTECTED]> wrote:
Robert Godfrey wrote:
> OK - so can we set a date for the creation of the M2 branch, and the
> merging
> of the 0-9 branch down to trunk?
We don't have to merge the entire branch in one shot, indeed I think
that would be very unwise. I strongly suggest that merging each
sub-project should be a separate effort. Making the branch must preceed
the merge efforts but it doesn't have to coincide with them.
> Would early next week (Monday or Tuesday) be OK with everybody for
> instance?
I can wait till Monday, but I don't want to wait longer than that.
> In the meantime we won't do anything new to trunk other than check in
> things
> we are working on, or fix bugs?
I would like to merge 0-9 python, it's fully compatible and it's one
less piece to worry about.
> Thoughts?
I see no reason to delay making the branch. It enables forward movement
of projects that are ready to move, and it doesn't impose anything on
projects that are not.
Cheers,
Alan.
The only difference with creating the M2 branch now and M1 is that
when we made M1 the code was done. Here we are saying we want to do M2
based on this code.
We can obviously take a branch from any revision point in the SVN
history so whiter we do it now or later doesn't really make much
difference. It would be good to get general agreement via the vote
that performing a release is something that we want to do. I don't
think there will be any real objections to working for a release after
all releasing code is a good thing.
--
Martin Ritchie
