I think we can wait a month. We don't have that many new features to release that we can't wait a month.
Unless the downstream projects requires the oposite, I'd say we wait. On Mon, Dec 6, 2010 at 11:41 AM, Guillaume Nodet <[email protected]> wrote: > Just started a discussion on the aries dev list for a release, and > given aries will graduate in december, they'd like to wait for that to > do a full 1.0 release in january... > Do we want to wait for that ? > > On Fri, Nov 26, 2010 at 18:27, Jamie G. <[email protected]> wrote: > > Hi All, > > > > Since our 2.1.0 release in September we have produced two patch > > releases along the 2.1.x branch. I believe it is now time to switch > > focus on preparing things for an up coming 2.2.0 release :) > > > > I have already setup a Jira entry for tracking 2.2.0 issues & tasks > > [1]. Over the next few days I and other community members will be > > reviewing issues left in our Jira marked for 2.2.0 and other issues > > that we think need to be included. In the mean time I would like to > > start the discussion surrounding a target date to produce 2.2.0 and > > subsequently create the 2.2.x maintenance branch (trunk becoming 2.3 > > snapshot line for new features, etc)? > > > > J > > > > 1. https://issues.apache.org/jira/browse/KARAF-249 > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- *Ioannis Canellos* http://iocanel.blogspot.com Integration Engineer @ Upstream S.A. <http://www.upstreamsystems.com>
