"Vincent Massol" <[EMAIL PROTECTED]> wrote on 21/11/2003 03:19:46 AM:
> > The next release for us is 1.0, not 1.1-SNAPSHOT. We haven't had a 1.0 > > yet. > > Yes, of course. But are you saying nobody is allowed to develop for the > following release (1.1) before 1.0 is released? As it is very bad form > to add new stuff to a RC release (only bugfixes are allowed), where do > you suggest people commit new stuff? Somewhere other than HEAD? That > looks really weird as the latest stuff is expected to be on HEAD... If you want to work on 1.1 now, I'm happy to create a 1_0 branch and work in there. Is this really what you want? There are lots of features scheduled for 1.0 already in Jira (see http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10030&fixfor=10211 ) , but I don't remember POMv4 being one of them. It seems that up until now, 1.1 has had noone working on it, and this is our opportunity to start that work. [snip] > Where do you commit new stuff that happens between the phase where you > have RC on HEAD? You theoretically don't have that long between RC and release. > Why? What are other's experience? AFAIK, there's no better way, > especially for projects like Maven where it takes several months between > a RC and a release. Agreed. The time between RCs and 1.0 means that if someone wants to start work on 1.1 or even 2.0 for that matter, a branch is the best way. My personal priority is a stable 1.0 release. I've been working for months to get to that point and don't want to stop now. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
