JBoss Cache 2.2.0

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
manikjboss.org






_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

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
> manikjboss.org
> 
> 
> 
> 
> 
> 
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-devlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev

-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberryredhat.com
_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

On 18 Mar 2008, at 15:12, Brian Stansberry wrote:
> 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.

Yeah, fair play - It's just that whether that bug fix
release is 2.1.1  
(once anything marked critical for 2.2.0 is done) or
2.2.0.GA, but  
that depends on timeframe.

- Manik

--
Manik Surtani
Lead, JBoss Cache
manikjboss.org






_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

My number one goal for 2.2 is array interception, and a few
minor 
enhancements. The array interception code is in place, most
of my work 
will be on fixing javassist and AOP, so we will need to do a
dependency 
change for 2.2 as well.

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
> manikjboss.org
> 
> 
> 
> 
> 
> 
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-devlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev


-- 
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

Manik Surtani wrote:
> 
> On 18 Mar 2008, at 15:12, Brian Stansberry wrote:
>> 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.
> 
> Yeah, fair play - It's just that whether that bug fix
release is 2.1.1 
> (once anything marked critical for 2.2.0 is done) or
2.2.0.GA, but that 
> depends on timeframe.
> 

I think the timeframe is fairly short for AS 5. It was
supposed to be 
last Friday.  There are still a lot of other projects still
outstanding, 
so it has slipped to ???. But I definitely feel Dimitris'
pain; he needs 
to get the external dependencies locked down.

-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberryredhat.com
_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

Is array interception critical for AS 5? I'm guessing no,
otherwise it  
would have been in the 2.1.0 feature list.  

On 18 Mar 2008, at 15:34, Jason T. Greene wrote:
> My number one goal for 2.2 is array interception, and a
few minor  
> enhancements. The array interception code is in place,
most of my  
> work will be on fixing javassist and AOP, so we will
need to do a  
> dependency change for 2.2 as well.
>
> 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
>> manikjboss.org
>> _______________________________________________
>> jbosscache-dev mailing list
>> jbosscache-devlists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
>
> -- 
> Jason T. Greene
> JBoss, a division of Red Hat

--
Manik Surtani
Lead, JBoss Cache
manikjboss.org






_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev

It is definitely desired for AS5 (would further improve
field based 
replication), but it's not worth holding back the AS5
release.

Manik Surtani wrote:
> Is array interception critical for AS 5? I'm guessing
no, otherwise it 
> would have been in the 2.1.0 feature list.  
> 
> On 18 Mar 2008, at 15:34, Jason T. Greene wrote:
>> My number one goal for 2.2 is array interception,
and a few minor 
>> enhancements. The array interception code is in
place, most of my work 
>> will be on fixing javassist and AOP, so we will
need to do a 
>> dependency change for 2.2 as well.
>>
>> 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
>>> manikjboss.org
>>>
_______________________________________________
>>> jbosscache-dev mailing list
>>> jbosscache-devlists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>>
>>
>> -- 
>> Jason T. Greene
>> JBoss, a division of Red Hat
> 
> -- 
> Manik Surtani
> Lead, JBoss Cache
> manikjboss.org
> 
> 
> 
> 
> 
> 


-- 
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jbosscache-dev mailing list
jbosscache-devlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev