On Nov 12, 2012, at 6:44 AM, David Bosschaert <[email protected]> wrote:
> Hi Christian, > > Sounds great and I think the work you've done and the work you're > proposing to do is a great step forward. > > However, some of the features that you've planned are fairly large, > and I would wonder whether it's feasible to have them all added and > stable within 2 weeks. > Would it not be better to implement all of these first and then call > for the release when it's all ready? > > Alternatively, if, for some reason you are unable to finish all of the > work that you're planning to do, we could still do a release with the > features that made it and delay the other ones to an later release, > IMHO… Personally, I kind of prefer that latter. The DOSGi stuff has been kind of languishing a bit. If we can start a process of smaller, incremental but more often releases that add stuff in, I'd be much happier. Getting things into the hands of the users sooner isn't a bad thing. :-) The entire Release Early, Release Often mantra. Dan > > Cheers, > > David > > On 12 November 2012 10:04, Christian Schneider <[email protected]> > wrote: >> Hi all, >> >> There are a lot of new features in the CXF DOSGi implementation. I would >> like to do a release of DOSGi in about two weeks. What do you think >> about it? >> Here are the done and planned features. >> >> Highlights: >> - Karaf Feature file for DOSGi >> - Reconnection support for Zookeeper discovery >> >> I am planning to do these additional features before the release: >> - Switch logging to slf4j-api >> - Use pax logging for all distributions >> - Support Zookeeper in Cluster mode >> - Remove Spring dependency (switch intention map support to OSGi service) >> >> Christian >> >> Here are the detailed issues: >> https://issues.apache.org/jira/browse/DOSGI/fixforversion/12319877#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel >> >> -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
