You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Anders Hammar <an...@hammar.net> on 2012/11/28 21:07:05 UTC
Versions in the MARCHETYPES JIRA project
I see we have different formats of the versions in the MARCHETYPES project
in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
If I fix a ticket, what should I set the fix versions as? Are we going to
keep separate release flows for each component or are we going to release
them all together? I would say releasing them separately is a lot of
overhead work.
/Anders
Re: Versions in the MARCHETYPES JIRA project
Posted by Anders Hammar <an...@hammar.net>.
> Ok, separate releases it is then. I'll do some cleaning in the JIRA
> project.
>
Eh, I spoke too soon. There's quite a mess in that project. The "5" version
is not just for the parent but other things as well.
I'm thinking we just remove the 1.1, 1.2, and 5 versions and do it right
from here. There is currently only 14 closed ticket, and those that will
loose a fix version could get back-tracked if it would turn out to be of
interest (which I doubt). Anyone against?
>
> /Anders
>
>
>
> On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy <ol...@apache.org> wrote:
>
>> 2012/11/28 Anders Hammar <an...@hammar.net>:
>> > I see we have different formats of the versions in the MARCHETYPES
>> project
>> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
>> 5 is for parent pom
>> 1.1 was probably when all archetypes were released at the same time.
>> imho the format maven-archetype-plugin-1.2 is what we have to use now.
>> >
>> > If I fix a ticket, what should I set the fix versions as? Are we going
>> to
>> > keep separate release flows for each component or are we going to
>> release
>> > them all together? I would say releasing them separately is a lot of
>> > overhead work.
>> >
>> > /Anders
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: Versions in the MARCHETYPES JIRA project
Posted by Anders Hammar <an...@hammar.net>.
Btw, anyone against changing "5" to "parent-5" to remove some confusion
with the older "1.1" etc?
/Anders
On Wed, Nov 28, 2012 at 9:14 PM, Anders Hammar <an...@hammar.net> wrote:
> Ok, separate releases it is then. I'll do some cleaning in the JIRA
> project.
>
> /Anders
>
>
>
> On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy <ol...@apache.org> wrote:
>
>> 2012/11/28 Anders Hammar <an...@hammar.net>:
>> > I see we have different formats of the versions in the MARCHETYPES
>> project
>> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
>> 5 is for parent pom
>> 1.1 was probably when all archetypes were released at the same time.
>> imho the format maven-archetype-plugin-1.2 is what we have to use now.
>> >
>> > If I fix a ticket, what should I set the fix versions as? Are we going
>> to
>> > keep separate release flows for each component or are we going to
>> release
>> > them all together? I would say releasing them separately is a lot of
>> > overhead work.
>> >
>> > /Anders
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: Versions in the MARCHETYPES JIRA project
Posted by Anders Hammar <an...@hammar.net>.
Ok, separate releases it is then. I'll do some cleaning in the JIRA project.
/Anders
On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy <ol...@apache.org> wrote:
> 2012/11/28 Anders Hammar <an...@hammar.net>:
> > I see we have different formats of the versions in the MARCHETYPES
> project
> > in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
> 5 is for parent pom
> 1.1 was probably when all archetypes were released at the same time.
> imho the format maven-archetype-plugin-1.2 is what we have to use now.
> >
> > If I fix a ticket, what should I set the fix versions as? Are we going to
> > keep separate release flows for each component or are we going to release
> > them all together? I would say releasing them separately is a lot of
> > overhead work.
> >
> > /Anders
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Versions in the MARCHETYPES JIRA project
Posted by Olivier Lamy <ol...@apache.org>.
2012/11/28 Anders Hammar <an...@hammar.net>:
> I see we have different formats of the versions in the MARCHETYPES project
> in JIRA. I see "5", "1.1" and "maven-archetype-plugin-1.2" for example.
5 is for parent pom
1.1 was probably when all archetypes were released at the same time.
imho the format maven-archetype-plugin-1.2 is what we have to use now.
>
> If I fix a ticket, what should I set the fix versions as? Are we going to
> keep separate release flows for each component or are we going to release
> them all together? I would say releasing them separately is a lot of
> overhead work.
>
> /Anders
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org