As I said before I agree that we should release more often. I was not the one wanting to wait with the release, but someone (can't remember who right now) wanted us to wait - so we waited.
John Casey wrote: > I appreciate the fact that there's a strong release plan for the maven > parent POM, but why is one plugin release holding up the release of a > piece of metadata? It's not that this POM has any functionality that may > contain regressions, or that successive releases of components depending > on it couldn't reset the enforcer version as necessary (with comments > that it's an ad hoc measure) just to get the release of that component > done. > > IMO, this seems like more of the thinking that has led us into long, > long timelines for the core releases...and the timelines that everyone > in the community criticizes so strongly. Is there a compelling reason > why we can't take a more incremental approach? We could release version > 9 that would be correct-minus-the-anticipated-enforcer-fix, then release > enforcer, then release parent version 10...and, if we're on the ball, we > could do this in 9 days. The end result would be a 9-day window where > the parent pom might not be everything you want it to be (as opposed to > months, I suppose), the choice to modify locally or wait for parent > version 10 in any plugins wanting to do a release in that 9-day window, > and two new-ish versions of the parent POM out on the repo instead of > one. Anyone in their right mind, and with no warning to the contrary, > would use the latest released version of the parent when they upgrade > anyway, so version 9 will become obsolete and ignored very quickly if > things go to plan. > > I don't see a problem in this plan. > > I'm +1 for this release. > > We can and should use some of the time between now and the release of > the enforcer plugin (a prereq for parent 10) to discuss what else needs > to be in there, like the things that Vincent has mentioned. > > Just my 2 cents. > > -john > > --- > John Casey > Developer and PMC Member, Apache Maven (http://maven.apache.org) > Member, Apache Software Foundation > Blog: http://www.ejlife.net/blogs/buildchimp > > Dennis Lundberg wrote: >> Brian, why do you need to release maven-parent-9 to be able to do the >> enforcer release? >> >> We have been holding off the release of the parent so that we could get >> the new enforcer into the parent... >> >> Brian E. Fox wrote: >>> Take 2: I removed the enforcer version and the clirr checks. (see other >>> vote thread for reasons) >>> >>> >>> >>> I need to release the maven-parent v9 before I can do the enforcer >>> release. Since there isn't a project to track changes in jira, here are >>> the diffs since v8. It's mostly housekeeping and plugin lockdown: >>> >>> >>> >>> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2= >>> 693260&diff_format=h >>> >>> The pom is staged at: >>> http://people.apache.org/~brianf/stage/org/apache/maven/maven-parent/ >>> >>> >>> >>> Vote is open for 72hrs. >>> >>> >>> >>> +1 >>> >>> >>> >>> >>> >>> I will go forward and stage the enforcer release in the same repository. >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
