RE: MAVEN_RC1_STABLE branch

2003-08-14 Thread dion
Brett Porter <[EMAIL PROTECTED]> wrote on 08/08/2003 08:20:58 AM: > I'm confused. Bummer, I was trying to not confuse people. > My understanding is: > - So RC1_STABLE is the branch people should be using if they want to build > and use latest maven and do bits and pieces development Yes. > - HE

RE: MAVEN_RC1_STABLE branch

2003-08-14 Thread Brett Porter
> > - for RC1, all fixes on the branch will be merged down to HEAD > That depends on whether the fixes for RC1 will require what's > in HEAD or > not. I thought RC1 would come from HEAD because that's where the memory leak is fixed. Aside from that, once maven is in RC mode, the number of big ch

Re: MAVEN_RC1_STABLE branch

2003-08-11 Thread dion
Yes, there will be a merge. It's going to be hard work, but the changes should be very isolate. I'm all for the incremental update process you've described below. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Colin Sampaleanu <[EMAIL PROTECTED]> wrote o

RE: MAVEN_RC1_STABLE branch

2003-08-07 Thread Brett Porter
I'm confused. My understanding is: - So RC1_STABLE is the branch people should be using if they want to build and use latest maven and do bits and pieces development - HEAD will be full of upheaval like renaming all of the properties in plugins and likely be unstable until RC1 - for RC1, all fixes

Re: MAVEN_RC1_STABLE branch

2003-08-07 Thread Colin Sampaleanu
Are you expecting that this will be merged back into HEAD, or HEAD merged into this in the future? Unfortuntately I think your chance of merging 2 diverged branches (where ongoing work has gone on in both) with CVS is next to nil. What is probably more realistic is for Jason or whoever to do