Hmm.. seems inevitable I guess. As for the M2 work done so far, I understand we'd have to *move* it from the old trunk to the new trunk (not exactly doing it all over again). Since it's the 2nd time around, I hope we can run through it this time within a week.
Cheers Prasad On 5/7/06, Jeff Genender <[EMAIL PROTECTED]> wrote:
+1. I think trying to merge 1.1 to the current 1.2 trunk would be a nightmare, indeed. Moving aside 1.2 and making the 1.1 copy a new trunk is the best decision, IMHO. Matt Hogstrom wrote: > I think we're at the point where 1.1 needs to bake for a bit and we'll > release it in a few weeks. Since I expect that folks will want to get to > putting in new feature and functions for 1.2 I wanted to kick off a > thread to get that discussion going. > > I'm consolidating here my recollections of discussion on the list about > what to do. The idea that made the most sense to me was to move the > current trunk to another branch and copy the 1.1 branch to trunk. We'd > then have people merge their changes from the the old trunk to the new > and start on 1.2. > > I'm not sure about timing but it might be nice to have this work done > before Java One and the hackathons. > > Thoughts? > > Matt
