On Mar 12, 2013, at 8:28 PM, Andrei Pozolotin <[email protected]> wrote:
> Jamie: > > cant you make a case that RC is not really a release? If it is "distributed" via the mirror system and Maven central and stuff, it's a release and would need a vote. For anything else, we have (or should have) nightly SNAPSHOT builds that people can grab. Dan > > Andrei > > -------- Original Message -------- > Subject: Re: release by subsystem > From: Jamie G. <[email protected]> > To: [email protected] > Cc: Guillaume Nodet <[email protected]> > Date: Tue 12 Mar 2013 07:24:53 PM CDT >> Sorry for jumping in here, >> >> Apache builds require approval before release: >> http://www.apache.org/dev/release.html#approving-a-release >> >> As to release schedule, that's purely at the discretion of the >> community to my best understanding. >> >> Cheers, >> Jamie >> >> On Tue, Mar 12, 2013 at 9:49 PM, Andrei Pozolotin >> <[email protected]> wrote: >>> Guillaume: >>> >>> how about automatic, once a month, karaf RC-XXX release, w/o vote? >>> >>> Andrei. >>> >>> -------- Original Message -------- >>> Subject: Re: release by subsystem >>> From: Guillaume Nodet <[email protected]> >>> To: [email protected] <[email protected]> >>> Date: Tue 12 Mar 2013 06:24:24 PM CDT >>>> On Tue, Mar 12, 2013 at 11:03 PM, Andrei Pozolotin < >>>> [email protected]> wrote: >>>> >>>>> *Jean-Baptiste, Łukasz** >>>>> * >>>>> FYI: >>>>> >>>>> 1) I released a jenkins plugin which allows incremental cascaded >>>>> releases from any level of dependency tree: >>>>> >>>>> https://wiki.jenkins-ci.org/display/JENKINS/Maven+Cascade+Release+Plugin >>>> Thx for the heads up. >>>> >>>> >>>>> 2) I hope you can switch away from monolithic releases and release >>>>> karaf modules/subsystems on demand and often. >>>>> >>>> Releasing karaf is fairly easy, and we rarely are waiting for third party >>>> dependencies. >>>> When that happens, it's mostly because we have bugs waiting to be fixed. >>>> >>>> >>>>> 3) IIRC, the first time "3.0.0.RC1 will come out in 2 weeks" was >>>>> promised on this mailing list about 2 years back :-) >>>>> >>>> And this has nothing to do with the release process. Technically speaking, >>>> trunk or branches are mostly always in a releasable state. >>>> >>>> >>>>> Thank you, >>>>> >>>>> Andrei >>>>> >>>>> -------- Original Message -------- >>>>> Subject: Re: release by subsystem >>>>> From: Jean-Baptiste Onofré <[email protected]> >>>>> To: [email protected] >>>>> Date: Thu 07 Feb 2013 02:26:10 PM CST >>>>>> Hi Andrei, >>>>>> >>>>>> I understand your point. >>>>>> >>>>>> Some parts are really tight together. However, that's the purpose of >>>>>> the minimal distribution and framework: >>>>>> >>>>>> - framework should provide the most minimal Karaf container (however, >>>>>> it embeds Aries Blueprint for instance, as Karaf bundles use it) >>>>>> - minimal is a very lightweight Karaf container, the purpose is to let >>>>>> the user create a custom distribution on top of that. >>>>>> >>>>>> I'm listening all proposals to improve these distributions ! >>>>>> >>>>>> Regards >>>>>> JB >>>>>> >>>>>> On 02/07/2013 05:30 PM, Andrei Pozolotin wrote: >>>>>>> *Jean-Baptiste* >>>>>>> >>>>>>> I am curious if you envision to change karaf layout so release by >>>>>>> subsystem is possible. >>>>>>> >>>>>>> For example, if I use minimal sub set of karaf, which does not need >>>>>>> Aries, why should I wait for it? >>>>>>> >>>>>>> this is similar to how ops4j was partitioned way back, so there are >>>>>>> no monolithic Godzilla releases any more. >>>>>>> >>>>>>> Thank you, >>>>>>> >>>>>>> Andrei >>>>>>> >>>>>>> > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
