Generally I agree that we should aim for such a cycle.
I only hope it is possible as we depend a lot on other projects that we
bundle. So a lot of the time a release waits on fixes or releases in
upstream projects.
Christian
Am 08.10.2014 07:52, schrieb 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
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
