Hi all,
we had the following result about the Karaf 2.1.x EOL and stop the 2.1.x
Jenkins:
+1 (binding): Andreas Pieber, Achim Nierbeck, Guillaume Nodet,
Jean-Baptiste Onofré, Christian Schneider, Freeman Fang, Charles Mouilliard
+1 (non-binding): Mike Van Geertruy, Johan Edstrom, Claus Ibsen
Jamie and I will cut off the Karaf 2.1.6 release which will be the last
Karaf 2.1.x branch release.
Karaf 2.1.x is not EndOfLife, and I'm going to disable the Jenkins build.
Thanks
Regards
JB
On 07/13/2011 01:12 PM, Jean-Baptiste Onofré wrote:
Thanks for the update Jamie.
I will send an e-mail to the user mailing list to inform the community.
Regards
JB
On 07/13/2011 12:50 PM, Jamie G. wrote:
It sounds like we have a consensus regarding option 1 and
de-allocating the jenkins profile for 2.1.x once we have 2.1.6
released.
I've created a release task for 2.1.6 here:
https://issues.apache.org/jira/browse/KARAF-734
As discussed on the IRC chat room, we can always come back after the
stated EOL release with an emergency patch if the community requires
it. This EOL statement is more about signaling to users that the
community is encouraging them to move along to newer versions, as
regularly scheduled patches are not planned. Perhaps there is a better
term for the idea than EOL?
Regardless of the terminology, the rational will have to be
communicated to the users list so that they can make forward plans.
Cheers,
Jamie
On Wed, Jul 13, 2011 at 4:00 AM, Claus Ibsen<[email protected]>
wrote:
Non binding and I too think EOL of 2.1 is okay. Its a bit fast though
for a project that is just 1 year old.
+1 for option 1.
There may be Camel and SMX users who are on Karaf 2.1. And they don't
migrate to new releases so often.
But I guess we can find out to help them if a critical issues is
discovered in the 2.1 codebase.
Camel 2.8 is now on Karaf 2.2.2 so future Camel releases should be safe.
On Wed, Jul 13, 2011 at 3:22 AM, Johan Edstrom<[email protected]> wrote:
Non binding but I think EOL is great.
+1 for option 1.
/je
On Jul 12, 2011, at 7:18 PM, Freeman Fang wrote:
+1 for option 1.
Freeman
On 2011-7-13, at 上午2:30, Jamie G. wrote:
Hi All,
As the 3.0.0 release draws near we'll be moving the 2.x branches to
maintenance mode. I think as we do this we should consider the
fate of
the last 2.1.x release version. Currently there are 5 resolved issued
in JIRA, with no outstanding items on 2.1.6. I would like to propose
two options;
1) Release 2.1.6 and mark it in JIRA as the EOL (no entry for
2.1.7). Or,
2) Leave it open in JIRA, and mark the version in JIRA as EOL, not to
be released.
Regardless of which choice we opt for, I think that we should
de-allocate the jenkins profile as we're not actively developing the
branch (https://builds.apache.org/job/Karaf-2.1.x/). We'll of course
create new profile for 3.0.x and 3.1.x once those branches are
available.
Cheers,
Jamie
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
--
Claus Ibsen
-----------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
