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 <[email protected]>: > +1 for Jason's procedure. > > Regards > Mirko > -- > Sent from my mobile > Am 30.05.2015 17:18 schrieb "Jason van Zyl" <[email protected]>: > > > 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 < > > [email protected]> 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
