> -----Original Message----- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 20 November 2003 22:35 > To: Maven Developers List > Subject: RE: [VOTE] Make groupId mandatory for POM version 4? > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 20, 2003 4:14 PM > [...] > > > > > I think we need to talk about my comments above on letting users > > access v4 > > features in a v3 POM. > > > > I think we should talk about timing. I don't think introducing a new POM > > version in a RC to release cycle is wise. > > > > +10!!! ( I cannot agree more) > I also think all those changes are badly needed but it is a mistake to > introduce them right now at this particular moment in time. > And another branch is the last thing we need right now IMHO. We have > already > enough mess with two existing branches.
This I agree but it has nothing to do with the subject of this mail. I'll tell you what is bad. Working for new stuff on a branch other than HEAD where everyone else is committing away. Why? Because everyone else is using HEAD for new stuff and you have to play catch up on your branch and keep merging stuff in a bi-directional way. Another branch for new stuff should only be used for really experimental stuff, usually for trying complete new architectures. It's usually only proof of concepts as it can almost never be merged back. It's for revolutions. Apart from this "special" example, alll new stuff should get committed to HEAD. What should happen is the following: - only commit bug fixes on a RC2 branch (I'm NOT talking about the rc2_unstable branch). Whenever you commit a bugfix there you also merge it in HEAD. This merge does not have to be done all the time but it's simpler. Remember that only bug fixes should be done on the RC2 branch so that shouldn't be much. - make all new changes (i.e. everything that is not a bug fix) on HEAD > BTW: Why we need new branch? Because this is the way it works with an SCM! > Why simply don't have two folders like: maven, maven-experimental. Sure, and you're volunteering to do the manual merge? :-) > if we need a place for code which will be not used in 1.0, and maybe will > be > used in 1.1 or 2.0 or whatever will come next we can use maven- > experimental. > Vincent's code related to POM 4 can go there. BTW, this is not experimental code. This is 1.1-SNAPSHOT code... ;-) Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
