"Vincent Massol" <[EMAIL PROTECTED]> wrote on 20/11/2003 08:05:18 PM:
> I guess it all depends on the question of whether we wish to link POM > versions to Maven releases. I think, I'm being swayed and I agree it's > cleaner to link them.... > > <thinking some more> > > Ok, I think I've realized what the problem is: We are developing 1.0-RC1 > on HEAD. This is the main problem. Normally here's how I would expect > development to work: > > - HEAD always contains latest development for the *next* release (that > would be 1.1-SNAPSHOT for us) The next release for us is 1.0, not 1.1-SNAPSHOT. We haven't had a 1.0 yet. > - Once a beta is released, CVS is branched (that would be > MAVEN_1_0_BRANCH for us) and bug fixing happens on that branch while > development for the next release continues on HEAD. For us the beta > period has lasted too long but we could say that RC goes into a branch. This isn't typical for other projects I've been involved with at Apache. They typically: - Do beta and RC work on HEAD - Once a release is made, create the branch. - HEAD becomes the workspace for the next release. - Changes to the release happen on the branch, but no active development typically happens there. > Should this happen (i.e. move RC1 to a branch and start 1.1 dev on HEAD) > then I'm happy to roll back all my changes related to POM4 and commit > them on HEAD (1.1-SNAPSHOT). > > What do you say? Please, lets not do this? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
