You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2015/10/30 13:16:35 UTC

Maven Release Version Policy

Hey, so...

Do we want to accept this implementation I knocked together:
https://github.com/CloudBees-community/cloudbees-maven-release-version-policy

If not I'm fine leaving it where it is... but I can get it donated to
the ASF if there is interest

-Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
ok great!

IIUC, it calculates version per package, based on automatic API  comparison

for release plugin, we need to calculate a version of the whole artifact. And 
since it's java, not OSGi, then there is no strict separation between API and 
internal details, I fear such approach won't give a good result: it will often 
find a difference in internal details

for whole artifact, when the more I think about it, the more I fear there is 
no real (automagic) automation possible:
- some changes are internal, then are not to be taken into account
- some functional changes don't have any visible impact on API

Regards,

Hervé

Le samedi 31 octobre 2015 13:45:20 Uwe Barthel a écrit :
> > great: what is the bundle-maven-plugin feature you're talking about?
> 
> The ‘baseline’[1] goal.
> It based on the BND Tool[2] (by Peter Kriens), gets the previous release (!)
> and check the difference between the byte code. Following semver, any new
> method (new feature) requires a new minor change. Changes in Interfaces or
> method signatures are incompatible and forces a major change. It is a bit
> more complex but not rocket science. :-)
> 
> [1]
> http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-3.0.0/do
> c/site/baseline-mojo.html [2] http://www.aqute.biz/Bnd/Versioning
> 
> mit freundlichen Grüßen
> Uwe Barthel
> 
> > On 31 Oct 2015, at 13:26, Hervé BOUTEMY <he...@free.fr> wrote:
> > 
> > great: what is the bundle-maven-plugin feature you're talking about?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 31 octobre 2015 13:18:35 Uwe Barthel a écrit :
> >>> I'm not sure "strict semver" can be automated: functional change can't
> >>> be
> >>> easily detected if there is no API change
> >> 
> >> The bundle-maven-plugin behaviour is a good base to discuss about I
> >> think.
> >> 
> >> mit freundlichen Grüßen
> >> Uwe Barthel
> >> 
> >>> On 31 Oct 2015, at 12:32, Hervé BOUTEMY <he...@free.fr> wrote:
> >>> 
> >>> I'm not sure "strict semver" can be automated: functional change can't
> >>> be
> >>> easily detected if there is no API change
> >>> 
> >>> semver is a great buzzword, but we should try to explain more precisely
> >>> what can be automated in the plugin to try to follow the buzzword
> >>> 
> >>> Regards,
> >>> 
> >>> Hervé
> >>> 
> >>> Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit :
> >>>> Hi,
> >>>> 
> >>>> I’m with Jason to move Maven forward to use (strict) semver as default
> >>>> version strategy.
> >>>> 
> >>>> I understand the 'cloudbee' strategy as a more exotic way.
> >>>> But I'm interested in more than one strategy, configurable via plugin
> >>>> or
> >>>> providing by default plugin.
> >>>> 
> >>>> mit freundlichen Grüßen
> >>>> Uwe Barthel
> >>> 
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >> 
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Uwe Barthel <ba...@x-reizend.de>.
> great: what is the bundle-maven-plugin feature you're talking about?
The ‘baseline’[1] goal.
It based on the BND Tool[2] (by Peter Kriens), gets the previous release (!) and check the difference between the byte code.
Following semver, any new method (new feature) requires a new minor change. Changes in Interfaces or method signatures are incompatible and forces a major change.
It is a bit more complex but not rocket science. :-)

[1] http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-3.0.0/doc/site/baseline-mojo.html
[2] http://www.aqute.biz/Bnd/Versioning

mit freundlichen Grüßen
Uwe Barthel
-- 
barthel@x-reizend.de


> On 31 Oct 2015, at 13:26, Hervé BOUTEMY <he...@free.fr> wrote:
> 
> great: what is the bundle-maven-plugin feature you're talking about?
> 
> Regards,
> 
> Hervé
> 
> Le samedi 31 octobre 2015 13:18:35 Uwe Barthel a écrit :
>>> I'm not sure "strict semver" can be automated: functional change can't be
>>> easily detected if there is no API change
>> 
>> The bundle-maven-plugin behaviour is a good base to discuss about I think.
>> 
>> mit freundlichen Grüßen
>> Uwe Barthel
>> 
>>> On 31 Oct 2015, at 12:32, Hervé BOUTEMY <he...@free.fr> wrote:
>>> 
>>> I'm not sure "strict semver" can be automated: functional change can't be
>>> easily detected if there is no API change
>>> 
>>> semver is a great buzzword, but we should try to explain more precisely
>>> what can be automated in the plugin to try to follow the buzzword
>>> 
>>> Regards,
>>> 
>>> Hervé
>>> 
>>> Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit :
>>>> Hi,
>>>> 
>>>> I’m with Jason to move Maven forward to use (strict) semver as default
>>>> version strategy.
>>>> 
>>>> I understand the 'cloudbee' strategy as a more exotic way.
>>>> But I'm interested in more than one strategy, configurable via plugin or
>>>> providing by default plugin.
>>>> 
>>>> mit freundlichen Grüßen
>>>> Uwe Barthel
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
great: what is the bundle-maven-plugin feature you're talking about?

Regards,

Hervé

Le samedi 31 octobre 2015 13:18:35 Uwe Barthel a écrit :
> > I'm not sure "strict semver" can be automated: functional change can't be
> > easily detected if there is no API change
> 
> The bundle-maven-plugin behaviour is a good base to discuss about I think.
> 
> mit freundlichen Grüßen
> Uwe Barthel
> 
> > On 31 Oct 2015, at 12:32, Hervé BOUTEMY <he...@free.fr> wrote:
> > 
> > I'm not sure "strict semver" can be automated: functional change can't be
> > easily detected if there is no API change
> > 
> > semver is a great buzzword, but we should try to explain more precisely
> > what can be automated in the plugin to try to follow the buzzword
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit :
> >> Hi,
> >> 
> >> I’m with Jason to move Maven forward to use (strict) semver as default
> >> version strategy.
> >> 
> >> I understand the 'cloudbee' strategy as a more exotic way.
> >> But I'm interested in more than one strategy, configurable via plugin or
> >> providing by default plugin.
> >> 
> >> mit freundlichen Grüßen
> >> Uwe Barthel
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Uwe Barthel <ba...@x-reizend.de>.
> I'm not sure "strict semver" can be automated: functional change can't be 
> easily detected if there is no API change

The bundle-maven-plugin behaviour is a good base to discuss about I think.

mit freundlichen Grüßen
Uwe Barthel
-- 
barthel@x-reizend.de


> On 31 Oct 2015, at 12:32, Hervé BOUTEMY <he...@free.fr> wrote:
> 
> I'm not sure "strict semver" can be automated: functional change can't be 
> easily detected if there is no API change
> 
> semver is a great buzzword, but we should try to explain more precisely what 
> can be automated in the plugin to try to follow the buzzword
> 
> Regards,
> 
> Hervé
> 
> Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit :
>> Hi,
>> 
>> I’m with Jason to move Maven forward to use (strict) semver as default
>> version strategy.
>> 
>> I understand the 'cloudbee' strategy as a more exotic way.
>> But I'm interested in more than one strategy, configurable via plugin or
>> providing by default plugin.
>> 
>> mit freundlichen Grüßen
>> Uwe Barthel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
I'm not sure "strict semver" can be automated: functional change can't be 
easily detected if there is no API change

semver is a great buzzword, but we should try to explain more precisely what 
can be automated in the plugin to try to follow the buzzword

Regards,

Hervé

Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit :
> Hi,
> 
> I’m with Jason to move Maven forward to use (strict) semver as default
> version strategy.
> 
> I understand the 'cloudbee' strategy as a more exotic way.
> But I'm interested in more than one strategy, configurable via plugin or
> providing by default plugin.
> 
> mit freundlichen Grüßen
> Uwe Barthel


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Uwe Barthel <ba...@x-reizend.de>.
Hi,

I’m with Jason to move Maven forward to use (strict) semver as default version strategy.

I understand the 'cloudbee' strategy as a more exotic way.
But I'm interested in more than one strategy, configurable via plugin or providing by default plugin.

mit freundlichen Grüßen
Uwe Barthel
-- 
barthel@x-reizend.de

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Stephen Connolly <st...@gmail.com>.
On Saturday 31 October 2015, Hervé BOUTEMY <he...@free.fr> wrote:

> if there is a regression, why not just open a Jira issue and fix it?


IIRC when I pointed out the bug 6-9 months ago Robert or somebody said that
the new behaviour was by design...


>
> I had a look at code, and it seems there is not any unit test against
> default
> version policy
>
> Regards,
>
> Hervé
>
> Le samedi 31 octobre 2015 17:41:45 Stephen Connolly a écrit :
> > On Saturday 31 October 2015, Hervé BOUTEMY <herve.boutemy@free.fr
> <javascript:;>> wrote:
> > > I don't know what "Cloudbees conventions" are, and how they are
> superior
> > > to
> > > everything else = what I understand from the README
> >
> > I jusj had to put a readme quickly.
> >
> > It is basically increment the least significant segment (which is what
> the
> > release plugin *used* to do) I added some extra bits like if the last
> > segment is -alpha then that goes to -beta-1 and -beta goes to -rc-1
> >
> > In any case if moving the code to ASF I would be removing the CloudBees
> > references
> >
> > > if we were able to better describe this policy, and compare different
> > > policies,
> > > that would give a meaning to adding more and providing them by default
> in
> > > the
> > > plugin to let users configure in the plugin policy to match the
> effective
> > > convention they use
> > >
> > > So, as the code currently says "cloudbees convention" without saying
> what
> > > it
> > > is, but just that it fixes everything (which is an assertion I can't
> > > trust), I
> > > don't see the point in integrating it in the plugin
> > >
> > > but I see the interest in adding more version policies, describing
> them in
> > > a
> > > neutral way (= strictly what they do), to let end users choose an
> > > implementation matching their need (ie their effective convention)
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 30 octobre 2015 12:16:35 Stephen Connolly a écrit :
> > > > Hey, so...
> > >
> > > > Do we want to accept this implementation I knocked together:
> > >
> https://github.com/CloudBees-community/cloudbees-maven-release-version-pol
> > > ic>
> > > > y
> > > >
> > > > If not I'm fine leaving it where it is... but I can get it donated to
> > > > the ASF if there is interest
> > > >
> > > > -Stephen
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> <javascript:;> <javascript:;>
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;>
> > >
> > > <javascript:;>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> <javascript:;> <javascript:;>
> > > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;> <javascript:;>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>

-- 
Sent from my phone

Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
if there is a regression, why not just open a Jira issue and fix it?

I had a look at code, and it seems there is not any unit test against default 
version policy

Regards,

Hervé

Le samedi 31 octobre 2015 17:41:45 Stephen Connolly a écrit :
> On Saturday 31 October 2015, Hervé BOUTEMY <he...@free.fr> wrote:
> > I don't know what "Cloudbees conventions" are, and how they are superior
> > to
> > everything else = what I understand from the README
> 
> I jusj had to put a readme quickly.
> 
> It is basically increment the least significant segment (which is what the
> release plugin *used* to do) I added some extra bits like if the last
> segment is -alpha then that goes to -beta-1 and -beta goes to -rc-1
> 
> In any case if moving the code to ASF I would be removing the CloudBees
> references
> 
> > if we were able to better describe this policy, and compare different
> > policies,
> > that would give a meaning to adding more and providing them by default in
> > the
> > plugin to let users configure in the plugin policy to match the effective
> > convention they use
> > 
> > So, as the code currently says "cloudbees convention" without saying what
> > it
> > is, but just that it fixes everything (which is an assertion I can't
> > trust), I
> > don't see the point in integrating it in the plugin
> > 
> > but I see the interest in adding more version policies, describing them in
> > a
> > neutral way (= strictly what they do), to let end users choose an
> > implementation matching their need (ie their effective convention)
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le vendredi 30 octobre 2015 12:16:35 Stephen Connolly a écrit :
> > > Hey, so...
> > 
> > > Do we want to accept this implementation I knocked together:
> > https://github.com/CloudBees-community/cloudbees-maven-release-version-pol
> > ic> 
> > > y
> > > 
> > > If not I'm fine leaving it where it is... but I can get it donated to
> > > the ASF if there is interest
> > > 
> > > -Stephen
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > <javascript:;>
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> > For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Stephen Connolly <st...@gmail.com>.
On Saturday 31 October 2015, Hervé BOUTEMY <he...@free.fr> wrote:

> I don't know what "Cloudbees conventions" are, and how they are superior to
> everything else = what I understand from the README


I jusj had to put a readme quickly.

It is basically increment the least significant segment (which is what the
release plugin *used* to do) I added some extra bits like if the last
segment is -alpha then that goes to -beta-1 and -beta goes to -rc-1

In any case if moving the code to ASF I would be removing the CloudBees
references


>
> if we were able to better describe this policy, and compare different
> policies,
> that would give a meaning to adding more and providing them by default in
> the
> plugin to let users configure in the plugin policy to match the effective
> convention they use
>
> So, as the code currently says "cloudbees convention" without saying what
> it
> is, but just that it fixes everything (which is an assertion I can't
> trust), I
> don't see the point in integrating it in the plugin
>
> but I see the interest in adding more version policies, describing them in
> a
> neutral way (= strictly what they do), to let end users choose an
> implementation matching their need (ie their effective convention)
>
> Regards,
>
> Hervé
>
> Le vendredi 30 octobre 2015 12:16:35 Stephen Connolly a écrit :
> > Hey, so...
> >
> > Do we want to accept this implementation I knocked together:
> >
> https://github.com/CloudBees-community/cloudbees-maven-release-version-polic
> > y
> >
> > If not I'm fine leaving it where it is... but I can get it donated to
> > the ASF if there is interest
> >
> > -Stephen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>

-- 
Sent from my phone

Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
I don't know what "Cloudbees conventions" are, and how they are superior to 
everything else = what I understand from the README

if we were able to better describe this policy, and compare different policies, 
that would give a meaning to adding more and providing them by default in the 
plugin to let users configure in the plugin policy to match the effective 
convention they use

So, as the code currently says "cloudbees convention" without saying what it 
is, but just that it fixes everything (which is an assertion I can't trust), I 
don't see the point in integrating it in the plugin

but I see the interest in adding more version policies, describing them in a 
neutral way (= strictly what they do), to let end users choose an 
implementation matching their need (ie their effective convention)

Regards,

Hervé

Le vendredi 30 octobre 2015 12:16:35 Stephen Connolly a écrit :
> Hey, so...
> 
> Do we want to accept this implementation I knocked together:
> https://github.com/CloudBees-community/cloudbees-maven-release-version-polic
> y
> 
> If not I'm fine leaving it where it is... but I can get it donated to
> the ASF if there is interest
> 
> -Stephen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Uwe Barthel <ba...@x-reizend.de>.
> by that you mean you expect a version policy implementation that runs a 
> bytecode check against previous version (like clirr) then chooses to increase 
> major minor or patch digit?

Why not. But not choose automatically instead of warning or break the release.

I’m use the bundle-maven-plugin (baseline) for similar behaviour at build time.
But it is strong bundled on OSGi version philosophy.

mit freundlichen Grüßen
Uwe Barthel
-- 
barthel@x-reizend.de


> On 31 Oct 2015, at 12:28, Hervé BOUTEMY <he...@free.fr> wrote:
> 
> by that you mean you expect a version policy implementation that runs a 
> bytecode check against previous version (like clirr) then chooses to increase 
> major minor or patch digit?
> 
> Regards,
> 
> Hervé
> 
> Le vendredi 30 octobre 2015 07:33:45 Jason van Zyl a écrit :
>> I would prefer to move toward standard semver and identify where we’re not
>> strictly adhering. Is it strict semver?
>>> On Oct 30, 2015, at 5:16 AM, Stephen Connolly
>>> <st...@gmail.com> wrote:
>>> 
>>> Hey, so...
>>> 
>>> Do we want to accept this implementation I knocked together:
>>> https://github.com/CloudBees-community/cloudbees-maven-release-version-pol
>>> icy
>>> 
>>> If not I'm fine leaving it where it is... but I can get it donated to
>>> the ASF if there is interest
>>> 
>>> -Stephen
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>> 
>> the course of true love never did run smooth ...
>> 
>> -- Shakespeare
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Hervé BOUTEMY <he...@free.fr>.
by that you mean you expect a version policy implementation that runs a 
bytecode check against previous version (like clirr) then chooses to increase 
major minor or patch digit?

Regards,

Hervé

Le vendredi 30 octobre 2015 07:33:45 Jason van Zyl a écrit :
> I would prefer to move toward standard semver and identify where we’re not
> strictly adhering. Is it strict semver?
> > On Oct 30, 2015, at 5:16 AM, Stephen Connolly
> > <st...@gmail.com> wrote:
> > 
> > Hey, so...
> > 
> > Do we want to accept this implementation I knocked together:
> > https://github.com/CloudBees-community/cloudbees-maven-release-version-pol
> > icy
> > 
> > If not I'm fine leaving it where it is... but I can get it donated to
> > the ASF if there is interest
> > 
> > -Stephen
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
> 
> the course of true love never did run smooth ...
> 
>  -- Shakespeare
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Stephen Connolly <st...@gmail.com>.
Here are some thoughts I had on semver:
http://javaadventure.blogspot.ie/2014/09/version-numbers.html

In any case this code is just to provide a strategy that people can
choose to turn on.

I am not saying that this strategy should be the default, only that it
should be one of the *defaultS* that people are able to choose
between... now if people think that this is a better default than our
current default, that is a different debate.

And as to what strategy we *the maven project* should use for our
component releases, that is again a whole different debate.

I have long since abandoned hope of there being one version numbering
scheme to rule them all which was in part what lead me to develop
rule-sets for the versions-m-p:
http://www.mojohaus.org/versions-maven-plugin/rule.html

On 30 October 2015 at 14:33, Jason van Zyl <ja...@takari.io> wrote:
> I would prefer to move toward standard semver and identify where we’re not strictly adhering. Is it strict semver?
>
>> On Oct 30, 2015, at 5:16 AM, Stephen Connolly <st...@gmail.com> wrote:
>>
>> Hey, so...
>>
>> Do we want to accept this implementation I knocked together:
>> https://github.com/CloudBees-community/cloudbees-maven-release-version-policy
>>
>> If not I'm fine leaving it where it is... but I can get it donated to
>> the ASF if there is interest
>>
>> -Stephen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> the course of true love never did run smooth ...
>
>  -- Shakespeare
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven Release Version Policy

Posted by Jason van Zyl <ja...@takari.io>.
I would prefer to move toward standard semver and identify where we’re not strictly adhering. Is it strict semver?

> On Oct 30, 2015, at 5:16 AM, Stephen Connolly <st...@gmail.com> wrote:
> 
> Hey, so...
> 
> Do we want to accept this implementation I knocked together:
> https://github.com/CloudBees-community/cloudbees-maven-release-version-policy
> 
> If not I'm fine leaving it where it is... but I can get it donated to
> the ASF if there is interest
> 
> -Stephen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

the course of true love never did run smooth ...

 -- Shakespeare













---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org