I would be okay with releasing what we have now as 2.0-GA. Based on the JIRAs that have 2.0-rc1 or 2.0 in their target versions, there is one outstanding bug to do with Log4jServletContextListener (LOG4J2-359<https://issues.apache.org/jira/browse/LOG4J2-359>), and the rest are new feature requests. Personally, I think we can work on the OSGi stuff and the other feature requests after the 2.0-GA release. I would be okay with fixing that 359 in a subsequent release.
I think we should either pick a date, or select some _absolutely must have_ JIRAs and release 2.0 when they are done. Personally I kind of favor the date approach. (Items that are not resolved before that date go into a subsequent release.) How about: Jan 31 as our target 2.0 release date? Thoughts? PS The *real* problem is... which logo do we pick? ;-) Oh well, maybe we can start worrying about that one when we've fixed a release date. On Tue, Dec 3, 2013 at 8:44 PM, Gary Gregory <[email protected]> wrote: > I would be ok with another release, "rc" or "beta" the name is debatable, > sooner rather than later. I'm not sure what the other committees are doing > around the holidays, but it's usually a busy time for folks in the US and > elsewhere I imagine. > > Gary > > -------- Original message -------- > From: Francesco Chicchiriccò <[email protected]> > Date:12/03/2013 05:49 (GMT-05:00) > To: [email protected] > Subject: Any roadmap date for 2.0? > > Hi all, > is there already any planned release date for 2.0RC1? And what about 2.0? > > Thanks. > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > http://people.apache.org/~ilgrosso/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
