Re: [PROPOSAL] Karaf release cycle

[Paul Spencer]

As a user of Karaf, I would appreciate release cycle like the one you describe.

As a developer, this can complicate the development process because one may 
need to hold commits until required dependency is released. Or said another 
way, commits requiring an unreleased dependency are not allowed.  So please 
make sure procedures and guidelines are in place for your committers that 
support the release cycle without stifling the development process.

Paul Spencer


On Oct 8, 2014, at 1:52 AM, Jean-Baptiste Onofré  wrote:

> Hi all,
> 
> Users complained about the variable and long delays between Karaf releases. 
> It's a fair comment and it's something that we have to improve.
> 
> I propose the following new policy about the releases cycle:
> - for "active" branches (3.0.x and 2.4.x), I propose a release every 6 weeks, 
> with maximum extend to 8 weeks.
> - for "eol" and "maintenance" branches (2.2.x and 2.3.x), it's "on demand", 
> no strong cycle there.
> 
> WDYT ?
> 
> If everybody agrees, I will update the releases schedule page on the website.
> 
> Regards
> JB
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: [PROPOSAL] Karaf release cycle

[Matt Sicker]

Personally, without a really easy way to upgrade Karaf in place, frequent
releases can become a bit of a pain. That, or better documentation on how
to use the karaf-maven-plugin would help a lot in that regard.

On 8 October 2014 00:58, Sobkowiak, Krzysztof 
wrote:

> +1 good idea
>
> Regards
> Krzysztof
>
> On 08.10.2014 07:52, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > Users complained about the variable and long delays between Karaf
> > releases. It's a fair comment and it's something that we have to improve.
> >
> > I propose the following new policy about the releases cycle:
> > - for "active" branches (3.0.x and 2.4.x), I propose a release every 6
> > weeks, with maximum extend to 8 weeks.
> > - for "eol" and "maintenance" branches (2.2.x and 2.3.x), it's "on
> > demand", no strong cycle there.
> >
> > WDYT ?
> >
> > If everybody agrees, I will update the releases schedule page on the
> > website.
> >
> > Regards
> > JB
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Technical Architect @ Capgemini | Committer @ ASF
> Capgemini  | Software Solutions Center
>  | Wroclaw
> e-mail: krzys.sobkow...@gmail.com  |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
>



-- 
Matt Sicker 

Re: [PROPOSAL] Karaf release cycle

[Sobkowiak, Krzysztof]

+1 good idea

Regards
Krzysztof

On 08.10.2014 07:52, Jean-Baptiste Onofré wrote:
> Hi all,
>
> Users complained about the variable and long delays between Karaf
> releases. It's a fair comment and it's something that we have to improve.
>
> I propose the following new policy about the releases cycle:
> - for "active" branches (3.0.x and 2.4.x), I propose a release every 6
> weeks, with maximum extend to 8 weeks.
> - for "eol" and "maintenance" branches (2.2.x and 2.3.x), it's "on
> demand", no strong cycle there.
>
> WDYT ?
>
> If everybody agrees, I will update the releases schedule page on the
> website.
>
> Regards
> JB

-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini | Committer @ ASF
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

[PROPOSAL] Karaf release cycle

[Jean-Baptiste Onofré]

Hi all,

Users complained about the variable and long delays between Karaf 
releases. It's a fair comment and it's something that we have to improve.


I propose the following new policy about the releases cycle:
- for "active" branches (3.0.x and 2.4.x), I propose a release every 6 
weeks, with maximum extend to 8 weeks.
- for "eol" and "maintenance" branches (2.2.x and 2.3.x), it's "on 
demand", no strong cycle there.


WDYT ?

If everybody agrees, I will update the releases schedule page on the 
website.


Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com