Re: [jbosscache-dev] JBoss Cache 2.2.0
As far as the AS is concerned, the goal is a rock solid 2.1.0. A 2.2.0
in mid-May is too late for the community AS 5, and for EAP 5 built from
that I don't think they want to be adding new features. I know I don't
want anything new from core cache; I just care about bug fixes.
JBCACHE-1170 and JBCACHE-1310 are critical for getting out AS 5.0.0.CR1
and Hibernate 3.3.0.GA. There's going to be a need for a bug fix
release pretty soon.
Manik Surtani wrote:
Guys,
What do you think should be in 2.2.0, and what should be in 3.x? Not
just for Core, but POJO as well?
I think that 2.2.0 should be a very quick release, my target for GA
being mid-May or so, so we can get back on to 3.x tasks (some of which,
like MVCC, I will be doing in parallel to 2.2.0 tasks).
Brian, does this make sense, since the main goal of 2.2.0 is, apart from
some more refactoring and a few features, to be rock-solid for AS 5
(given the way AS 5 deadlines are moving). With GA targeted for
mid-May, I would think the first betas would start coming out in 2 - 3
weeks?
Main tasks for core cache:
- bug fixes reported on 2.1.0, inc. JBCACHE-1170, JBCACHE-1190,
JBCACHE-1258
- new features, inc. JBCACHE-789, JBCACHE-1262, JBCACHE-1273
- optimisations/refactoring, inc. JBCACHE-890, JBCACHE-611,
JBCACHE-1222, JBCACHE-1239,
Jason, what are your thoughts for POJO Cache?
Cheers
Manik
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com