Guys, With lukas we worked this afternoon of the maven 1.X roadmap. We selected the (few) issues we'll fix for the beta 3 of maven 1.1 in the core. We'll unschedule all the other issues (thus you'll receive a lot of notifications !!). We'll work on them (perhaps) in maven 1.2.X.
cheers arnaud On 4/12/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > Hi guys ! > > I didn't think I'll launch such a thread :-) > > I try to reply to everybody. > > - About the policy to release maven, as I already said it, I'm in favor > to use the same one as in tomcat, httpd, ... We release regularly a new > version and we vote for the stability : alpha / beta / stable. But we have a > little problem because actually maven doesn't support this usecase and we > have to do it manually. The major problem is that we began maven 1.1 with > the other policy and we already published some betas. Can we change in the > middle of the cycle ? Other problem : Can we have a different policy between > m1 and m2 ? I don't think so :-( PMCs, WDYT ? > > - About the roadmap. I quickly reorganized it because : > - As Brett said it, we don't have to define issues/enhancements/... in > a Release Candidate. A RC must be the image of the next release. > - I moved all bugs in the beta 3 because if we have to do something in > the core it's to fix bugs. I didn't yet study all of them and I don't know > if we'll fix all of them. What I know it's that we have several blocking > bugs that I already reproduced : > > - MAVEN-1751 <http://jira.codehaus.org/browse/MAVEN-1751> "A cycle > was detected" where no cycle can be > found<http://jira.codehaus.org/browse/MAVEN-1751> > - MAVEN-1750 <http://jira.codehaus.org/browse/MAVEN-1750> Can't use > two times a multiprojects in 2 differents > goals<http://jira.codehaus.org/browse/MAVEN-1750> > - MAVEN-1711 <http://jira.codehaus.org/browse/MAVEN-1711> Error > reading POM <http://jira.codehaus.org/browse/MAVEN-1711> > - MAVEN-1691 <http://jira.codehaus.org/browse/MAVEN-1691> Variable > scope problem <http://jira.codehaus.org/browse/MAVEN-1691> > - Backward incompability about XML entities usage : xerces must be > back :-( ( which will certainly produce some problems with the jdk > 1.5..) > - Plugins which are called from a postGoal (linkcheck, pdf...) seems > to be called only one time in a multiproject ! > > And much more for which I didn't yet take a look at. There are too much > problems with multiprojects. I hope that it doesn't come from our upgrade of > Jelly, otherwise we'll have to stand for a new release of it. Same thing > with Jaxen, Dom4J and Co. We had some problems with them :-( > For these reasons, I don't consider actually that maven 1.1 beta 2 or 1.1beta > 3-SNAPSHOT (today) are stable. > > - I moved all enhancements in a potential beta 4 because we have to > release the beta 3 ASAP. But it's not sure that we'll do a beta 4 and if we > do it that we'll do all these enhancements. We have to study them and see if > we need to do them (in the beta 4 ? in maven 1.2 ? never ??) > > Any thoughts ? > > Arnaud > > > > On 4/12/06, Brett Porter < [EMAIL PROTECTED]> wrote: > > > > If it's stable, then it should be 1.1 and things pushed off to 1.2, not > > called rc1 - that was really my point. > > > > The only reason I thought it might still be beta was because some things > > are still not stable (eg, is xerces back in yet?) > > > > - Brett > > > > Felipe Leme wrote: > > > Dion Gillard wrote: > > > > > >> In this context, I'd call 1.1 beta 2 a 'Stable' release. People are > > >> definitely using it as such. It's (in my mind anyways), v1.1.0. > > >> > > >> Since Maven is nothing without the plugins, upgrading those is reason > > >> enough > > >> for a new release (1.1.1). > > >> > > >> Thoughts? > > > > > > I'm a +1 - even though our main focus is on M2, a lot of people still > > > depends on Maven 1.x (and that's an unbiased opinion, as I'm not using > > > Maven 1.x anymore). > > > > > > -- Felipe > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
