On 2/8/13 12:26 PM, Mircea Markus wrote:
On 7 Feb 2013, at 11:36, Manik Surtani wrote:
> On 7 Feb 2013, at 11:29, Bela Ban <bban(a)redhat.com
> <mailto:bban@redhat.com>> wrote:
>
>> I meant to say that this is up to you guys to decide inwhich Infinispan
>> release this will be used, but it will be available in JGroups 3.3.
>>
>> What's the strategy/schedule for 6 and 5.3 anyway ?
>
> 5.3 will be relatively quick, just an incremental release mainly
> targeting reviewing and putting in a few contribs on the queue. E.g.,
> we're hoping for 5.3 to be feature-complete in no more than 2 months.
>
> 6 is where we get to break API - specifically with the new packaging,
> etc.
>
> But this seems like a pretty important feature/fix so it may make
> sense to get this into 5.3.
Pedro - please correct me if I'm wrong.
This feature (or the alternative Pedro has already implemented in his
branch) is used be the TO code that we'll integrate in 5.3. Se in
order to have TO in ISPN we need these jgroups improvements in.
yes, I'll need
it. otherwise, I have to create another RpcCommand to
send back the response generated by the other thread
Pedro - are there any other modifications in *your branch* of jgroups
that require integration into jgroups upstream from a TO perspective?
No, just
this...
Cheers
Pedro
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org <
http://www.infinispan.org>)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev