[jbosscache-dev] Re: 1.4.0.SP2 WAS: Customer wants a patch with JBCACHE-776 + JBCACHE-777. Working on it today, could you confirm fixes for them?

[Manik Surtani]

s/1.4.2.SP2/1.4.0.SP2


--
Manik Surtani

Lead, JBoss Cache
JBoss, a division of Red Hat

Email: manik at jboss.org
Telephone: +44 7786 702 706
MSN: manik at surtani.org
Yahoo/AIM/Skype: maniksurtani


On 27 Sep 2006, at 11:37, Manik Surtani wrote:

> This is what we have scheduled for 1.4.2.SP2:
>
> Bug
>
>     * [ JBCACHE-755 ] Potential bug when using (async) replication  
> queue and region based marshalling
>     * [ JBCACHE-760 ] TreeCacheListener in PojoCache gets  
> nodeModify events for invalid objects
>     * [ JBCACHE-765 ] implementation of equals() in collections is  
> incorrect
>     * [ JBCACHE-769 ] JDBCCacheLoader should not directly serialize  
> a map passed to put
>     * [ JBCACHE-776 ] EvictionPolicyProvider WARN message is noisy  
> and misleading
>     * [ JBCACHE-777 ] Creating a custom cache loader which  
> delegates to a standard cache loader, can generate misleading WARN  
> messages
>     * [ JBCACHE-785 ] InvocationContext and suspended transactions
>
> Task
>
>     * [ JBCACHE-761 ] Make connecting the channel and state  
> transfer an atomic part of startup
>
> Patch
>
>     * [ JBCACHE-766 ] Don't return unnecessary values from  
> _replicate, avoiding need for marshalling
>     * [ JBCACHE-767 ] Fail more silently when setting node versions
>
>
> Of these:
>
> * JBCACHE-785 and JBCACHE-761 are still open (but will be completed  
> before making such a release)
> * JBCACHE-766, JBCACHE-767, JBCACHE-776 and JBCACHE-777 are just  
> "optimisations"
>
> Do the rest, which are valid bug fixes, warrant a release yet?   
> What do people think?
>
> In terms of timescales, I could have the release tagged and ready  
> for QA by next week.
>
> Cheers,
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik at jboss.org
> Telephone: +44 7786 702 706
> MSN: manik at surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
> On 26 Sep 2006, at 14:00, Galder Zamarreno wrote:
>
>> Ok. I gave an idea to the customer of 2/3 which might be mistaken  
>> then, ups! :-$. Assuming that the customer would go down this  
>> route, how long would it take to release it?
>>
>> I guess it might also depend on Siemens and the atomic startup  
>> work that is going into 1.4.x.
>>
>> Galder Zamarreño
>> Support Engineer
>> JBoss, a division of Red Hat
>>
>>
>> -----Original Message-----
>> From: Manik Surtani [mailto:manik at jboss.org]
>> Sent: 26 September 2006 13:47
>> To: Galder Zamarreno
>> Cc: Brian Stansberry; Vladimir Blagojevic; jbosscache- 
>> dev at lists.jboss.org
>> Subject: 1.4.0.SP2 WAS: Customer wants a patch with JBCACHE-776 +  
>> JBCACHE-777. Working on it today, could you confirm fixes for them?
>>
>> No fixed release date on 1.4.0.SP2 ATM - don't see a pressing need.
>> What do people think?
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik at jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik at surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>> On 26 Sep 2006, at 10:57, Galder Zamarreno wrote:
>>
>>> Rel date for 1.4.0.SP2 is outdated:
>>> http://jira.jboss.com/jira/browse/JBCACHE?
>>> report=com.atlassian.jira.plugin.system.project:roadmap-panel
>>>
>>> Shall I tell him in the next 2/3 weeks?
>>>
>>> Galder Zamarreño
>>> Support Engineer
>>> JBoss, a division of Red Hat
>>>
>>
>> <SNIP>
>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev