You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kristian Rosenvold <kr...@zenior.no> on 2015/05/30 17:03:13 UTC
Releasing entire maven-shared as a single release ?
I've been wondering if we should just give every component in maven-shared
the same version number and always release all of the modules at the same
time.... ? (this would influence an upcoming git migration....)
Kristian
Re: Releasing entire maven-shared as a single release ?
Posted by Kristian Rosenvold <kr...@gmail.com>.
Mirko; I was thinking one stage, vote one for everything. But I realized
what I just want is for combined releases to "work" so we can have a "safe"
process that releases shared code and plugins in the same release. Right
now we have to break the build to to that.
K
2015-05-31 20:24 GMT+02:00 Mirko Friedenhagen <mf...@gmail.com>:
> Hello Kristian,
>
> sorry for asking, could you be more specific:
> - Should they all go to a common staging repository, so testing them
> together is easier.
> - Should there only be one vote process?
>
> What does combined mean for you here?
>
> Regards
> Mirko
> --
> Sent from my mobile
> Am 31.05.2015 10:38 schrieb "Kristian Rosenvold" <
> kristian.rosenvold@gmail.com>:
>
> > Oh well, I suppose what I /really/ want to fix is making combined
> releases
> > work.
> >
> > K
> >
> >
> > 2015-05-31 10:05 GMT+02:00 Mirko Friedenhagen <mf...@gmail.com>:
> >
> > > +1 for Jason's procedure.
> > >
> > > Regards
> > > Mirko
> > > --
> > > Sent from my mobile
> > > Am 30.05.2015 17:18 schrieb "Jason van Zyl" <ja...@takari.io>:
> > >
> > > > If they have truly separate development cycles, then I think it best
> to
> > > > try and move toward meaningful (semantic) versioning for each
> > component.
> > > > Which means they have their own version and are released
> individually.
> > > >
> > > > As part of the Git migration I think putting components that have
> their
> > > > own unique lifecycle into their its own repository is more the
> > direction
> > > we
> > > > need to go in. Grouping everything together and releasing them
> > together I
> > > > believe runs counter to having a good separation of concerns in
> > general.
> > > >
> > > > > On May 30, 2015, at 11:03 AM, Kristian Rosenvold <
> > > > kristian.rosenvold@zenior.no> wrote:
> > > > >
> > > > > I've been wondering if we should just give every component in
> > > > maven-shared
> > > > > the same version number and always release all of the modules at
> the
> > > same
> > > > > time.... ? (this would influence an upcoming git migration....)
> > > > >
> > > > >
> > > > > Kristian
> > > >
> > > > Thanks,
> > > >
> > > > Jason
> > > >
> > > > ----------------------------------------------------------
> > > > Jason van Zyl
> > > > Founder, Takari and Apache Maven
> > > > http://twitter.com/jvanzyl
> > > > http://twitter.com/takari_io
> > > > ---------------------------------------------------------
> > > >
> > > > happiness is like a butterfly: the more you chase it, the more it
> will
> > > > elude you, but if you turn your attention to other things, it will
> come
> > > > and sit softly on your shoulder ...
> > > >
> > > > -- Thoreau
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> >
>
Re: Releasing entire maven-shared as a single release ?
Posted by Mirko Friedenhagen <mf...@gmail.com>.
Hello Kristian,
sorry for asking, could you be more specific:
- Should they all go to a common staging repository, so testing them
together is easier.
- Should there only be one vote process?
What does combined mean for you here?
Regards
Mirko
--
Sent from my mobile
Am 31.05.2015 10:38 schrieb "Kristian Rosenvold" <
kristian.rosenvold@gmail.com>:
> Oh well, I suppose what I /really/ want to fix is making combined releases
> work.
>
> K
>
>
> 2015-05-31 10:05 GMT+02:00 Mirko Friedenhagen <mf...@gmail.com>:
>
> > +1 for Jason's procedure.
> >
> > Regards
> > Mirko
> > --
> > Sent from my mobile
> > Am 30.05.2015 17:18 schrieb "Jason van Zyl" <ja...@takari.io>:
> >
> > > If they have truly separate development cycles, then I think it best to
> > > try and move toward meaningful (semantic) versioning for each
> component.
> > > Which means they have their own version and are released individually.
> > >
> > > As part of the Git migration I think putting components that have their
> > > own unique lifecycle into their its own repository is more the
> direction
> > we
> > > need to go in. Grouping everything together and releasing them
> together I
> > > believe runs counter to having a good separation of concerns in
> general.
> > >
> > > > On May 30, 2015, at 11:03 AM, Kristian Rosenvold <
> > > kristian.rosenvold@zenior.no> wrote:
> > > >
> > > > I've been wondering if we should just give every component in
> > > maven-shared
> > > > the same version number and always release all of the modules at the
> > same
> > > > time.... ? (this would influence an upcoming git migration....)
> > > >
> > > >
> > > > Kristian
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> > > ----------------------------------------------------------
> > > Jason van Zyl
> > > Founder, Takari and Apache Maven
> > > http://twitter.com/jvanzyl
> > > http://twitter.com/takari_io
> > > ---------------------------------------------------------
> > >
> > > happiness is like a butterfly: the more you chase it, the more it will
> > > elude you, but if you turn your attention to other things, it will come
> > > and sit softly on your shoulder ...
> > >
> > > -- Thoreau
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
Re: Releasing entire maven-shared as a single release ?
Posted by Kristian Rosenvold <kr...@gmail.com>.
Oh well, I suppose what I /really/ want to fix is making combined releases
work.
K
2015-05-31 10:05 GMT+02:00 Mirko Friedenhagen <mf...@gmail.com>:
> +1 for Jason's procedure.
>
> Regards
> Mirko
> --
> Sent from my mobile
> Am 30.05.2015 17:18 schrieb "Jason van Zyl" <ja...@takari.io>:
>
> > If they have truly separate development cycles, then I think it best to
> > try and move toward meaningful (semantic) versioning for each component.
> > Which means they have their own version and are released individually.
> >
> > As part of the Git migration I think putting components that have their
> > own unique lifecycle into their its own repository is more the direction
> we
> > need to go in. Grouping everything together and releasing them together I
> > believe runs counter to having a good separation of concerns in general.
> >
> > > On May 30, 2015, at 11:03 AM, Kristian Rosenvold <
> > kristian.rosenvold@zenior.no> wrote:
> > >
> > > I've been wondering if we should just give every component in
> > maven-shared
> > > the same version number and always release all of the modules at the
> same
> > > time.... ? (this would influence an upcoming git migration....)
> > >
> > >
> > > Kristian
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Takari and Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > ---------------------------------------------------------
> >
> > happiness is like a butterfly: the more you chase it, the more it will
> > elude you, but if you turn your attention to other things, it will come
> > and sit softly on your shoulder ...
> >
> > -- Thoreau
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: Releasing entire maven-shared as a single release ?
Posted by Mirko Friedenhagen <mf...@gmail.com>.
+1 for Jason's procedure.
Regards
Mirko
--
Sent from my mobile
Am 30.05.2015 17:18 schrieb "Jason van Zyl" <ja...@takari.io>:
> If they have truly separate development cycles, then I think it best to
> try and move toward meaningful (semantic) versioning for each component.
> Which means they have their own version and are released individually.
>
> As part of the Git migration I think putting components that have their
> own unique lifecycle into their its own repository is more the direction we
> need to go in. Grouping everything together and releasing them together I
> believe runs counter to having a good separation of concerns in general.
>
> > On May 30, 2015, at 11:03 AM, Kristian Rosenvold <
> kristian.rosenvold@zenior.no> wrote:
> >
> > I've been wondering if we should just give every component in
> maven-shared
> > the same version number and always release all of the modules at the same
> > time.... ? (this would influence an upcoming git migration....)
> >
> >
> > Kristian
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
> -- Thoreau
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Releasing entire maven-shared as a single release ?
Posted by Fred Cooke <fr...@gmail.com>.
+1 from me, too! Well said.
On Sun, May 31, 2015 at 6:09 AM, Michael Osipov <mi...@apache.org> wrote:
> Am 2015-05-30 um 17:17 schrieb Jason van Zyl:
>
>> If they have truly separate development cycles, then I think it best to
>> try and move toward meaningful (semantic) versioning for each component.
>> Which means they have their own version and are released individually.
>>
>> As part of the Git migration I think putting components that have their
>> own unique lifecycle into their its own repository is more the direction we
>> need to go in. Grouping everything together and releasing them together I
>> believe runs counter to having a good separation of concerns in general.
>>
>>
> +1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Releasing entire maven-shared as a single release ?
Posted by Michael Osipov <mi...@apache.org>.
Am 2015-05-30 um 17:17 schrieb Jason van Zyl:
> If they have truly separate development cycles, then I think it best to try and move toward meaningful (semantic) versioning for each component. Which means they have their own version and are released individually.
>
> As part of the Git migration I think putting components that have their own unique lifecycle into their its own repository is more the direction we need to go in. Grouping everything together and releasing them together I believe runs counter to having a good separation of concerns in general.
>
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing entire maven-shared as a single release ?
Posted by Jason van Zyl <ja...@takari.io>.
If they have truly separate development cycles, then I think it best to try and move toward meaningful (semantic) versioning for each component. Which means they have their own version and are released individually.
As part of the Git migration I think putting components that have their own unique lifecycle into their its own repository is more the direction we need to go in. Grouping everything together and releasing them together I believe runs counter to having a good separation of concerns in general.
> On May 30, 2015, at 11:03 AM, Kristian Rosenvold <kr...@zenior.no> wrote:
>
> I've been wondering if we should just give every component in maven-shared
> the same version number and always release all of the modules at the same
> time.... ? (this would influence an upcoming git migration....)
>
>
> Kristian
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing entire maven-shared as a single release ?
Posted by Hervé BOUTEMY <he...@free.fr>.
if you look at shared content, there is so much diversity that it would not
make sense to release everything with 1 version
http://maven.apache.org/shared/index.html
there is also the special maven-reporting-api case where this would wreck
havoc
we'll need to find another idea
Regards,
Hervé
Le samedi 30 mai 2015 17:03:13 Kristian Rosenvold a écrit :
> I've been wondering if we should just give every component in maven-shared
> the same version number and always release all of the modules at the same
> time.... ? (this would influence an upcoming git migration....)
>
>
> Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org