I guess we need to clear up what I mean by a maintenance line... We *can/may* cut releases on maintenance / security line... Does not mean we *will* more that for non-security/maintenance lines there is ZERO possibility of us cutting a release...
On Sunday, 23 February 2014, Dennis Lundberg <denn...@apache.org> wrote: > I think the parts about which JRE to depend upon deserves its own > document, because it is something that affects our users much more > that which version numbers we use. The same goes for which version of > Maven Core a plugin/component can require. That being said, your > proposal is a great starting point for discussions about version > numbering. > > Maven Core > > Looking at our history for core, the 18 month rules in there are a bit > hard I think. That would mean that 3.0.x would be EOL now. Having a > fixed time is good, I just think that it needs to be longer. But that > also depends on our cadence of minor releases going forward. > > Maven Plugins > > The current proposal is a huge step from what we currently do, in > terms of version lines. I can't recall a single maintenance line or > security line from memory. The only maintenance line that I know of > has been for the Site Plugin, where we kept one the the previous MAJOR > version, i.e. 2.x. > > Provided we do not change Maven version or Java version I think that > we can live with just a development line. Should any security > vulnerabilities be found, we can just fix it in trunk and release a > patch version. Or if to much has happened on trunk, create branch from > the previous MAJOR.MINOR and do a patch release from it. > > Maven Shared Components > As for plugins the proposal is a big step from what we do today. Do we > have the time and man hours to maintain for example four versions of > wagon? > > > On Fri, Feb 21, 2014 at 4:10 PM, Stephen Connolly > <stephen.alan.conno...@gmail.com <javascript:;>> wrote: > > For discussion... and tearing into... and Chris shouting out that IBM > > supports Java 6 for yonks... > > > > https://cwiki.apache.org/confluence/display/MAVEN/Version+number+policy > > > > I think we need a version policy and the best way to get one is to put a > > draft together and let people edit it to something that we all can be > happy > > with. > > > > Constructive feedback welcome... in fact committers editing the doc is > > encouraged... > > > > Please leave the DRAFT heading at the top. > > > > If a consensus emerges we will have a vote and put the resulting policy > on > > the project site as opposed to a draft document on the wiki. > > > > -Stephen > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@maven.apache.org <javascript:;> > > -- Sent from my phone
