I've created the following Jira entries to track the currently planned releases:
Apache Karaf 2.1.1: https://issues.apache.org/jira/browse/KARAF-248 Apache Karaf 2.2.0: https://issues.apache.org/jira/browse/KARAF-249 I'm more than happy to pick up RM duties on these releases. As to a timeline for these releases I'm very open to suggestion. I'll concentrate first on identifying issues for 2.1.1 inclusion while the 2.2.0 trunk continues. On Thu, Oct 14, 2010 at 6:50 AM, Guillaume Nodet <[email protected]> wrote: > Sounds like a good plan. > I think we should also start thinking about what we want to include in 2.2, > but we could also do a time-constrained release and just fix a date and > release with whatever has been put in trunk (provided it's stable enough of > course). > > On Wed, Oct 13, 2010 at 16:43, Jamie G. <[email protected]> wrote: > > > Hi All, > > > > Now that Karaf 2.1.0 is available we have had some issues reported > against > > it, and as such we have begun to remediate those issues. This leads to > the > > important question of how do we want to wrap up these fixes? Should we > pick > > up the 2.1.x branch and prepare a 2.1.1 release or save all these fixes > and > > roll them into the 2.2.0 release? > > > > Personally I think that if we do a 2.1.x maintenance release then we can > > allow trunk (2.2.0) to continue along a little longer with more new > feature > > development. > > > > As to the 2.2.0 release, we need to begin planning a target date for when > > we'd like to cut a release candidate. I'd prefer to have this occur no > > later > > than early December in order to avoid end of year holiday scheduling > > conflicts. > > > > Cheers, > > Jamie > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
