Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-24 Thread Anders Hammar
First, thanks Stephen (and others) for working on this. I think it's very important that we use version numbers consistently and also communicate what they mean to our users. We should also be very clear with what to expect. I agree with Dennis and Brett here, I think we could simplify by just sta

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-23 Thread Brett Porter
On 24 Feb 2014, at 2:48 am, Stephen Connolly wrote: > 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

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-23 Thread Stephen Connolly
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 wrot

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-23 Thread Dennis Lundberg
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 po

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-21 Thread Baptiste Mathus
Le 21 févr. 2014 16:39, "Igor Fedorenko" a écrit : > > I think this is reasonable. > > One observation. Maven does not have an API, plugins and projects can > access pretty much anything from the core. Add to this three distinct > user communities -- (end) users, plugin developers and embedders --

Re: [DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-21 Thread Igor Fedorenko
I think this is reasonable. One observation. Maven does not have an API, plugins and projects can access pretty much anything from the core. Add to this three distinct user communities -- (end) users, plugin developers and embedders -- and I think pretty much any change will break somebody. This

[DISCUSS] Adopt a version policy and a support policy to go with it.

2014-02-21 Thread Stephen Connolly
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 th