+1
Christian
Am 15.03.2012 16:51, schrieb Guillaume Nodet:
And I think the time between 2.2 and 3.0 is way too long and I'd like to
have more smaller releases than targeting major releases, especially if
they are compatible.
On Thu, Mar 15, 2012 at 16:48, Guillaume Nodet<[email protected]> wrote:
Karaf is not really tied to the osgi version used underneath, especially
as they are backward compatible and I don't think upgrading the underlying
OSGi container warrant a new major release which is very painful for
downstream projects. I think a Karaf 3.1 would be sufficient for including
the new osgi version.
Ftr, I'm still thinking about create a 2.3 branch in the near future to
backport some new features that came into 3.x, including the upgrade to
osgi 4.3 to the 2.x branch, but leaving all disruptive features around the
maven plugin, subshells, command renaming, etc...
Just my 2 cents.
On Thu, Mar 15, 2012 at 16:01, Jamie G.<[email protected]> wrote:
Hi All,
As there is already some discussion surrounding the next major OSGi
core specification, in anticipation I think we should consider adding
to our project Jira a place holder for Karaf version 4.0.0.
Version 4.0.0 of Karaf would be for Karaf centring around OSGi R5.
Karaf 3.x currently is centred on OSGi 4.3, while Karaf 2.x continues
to focus on OSGi R4.2. I believe having this roadmap would help make
the forward progress of Karaf a little clearer to our users.
The above being said, our community focus is still on Karaf 3.0.0. I
think just having a version place holder in Jira now will allow us to
enter issues related to OSGi R5 when required.
Any thoughts?
[1] http://www.osgi.org/blog/
Cheers,
Jamie
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
FuseSource, Integration everywhere
http://fusesource.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
