[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?

Manic, Have you got any updates regarding this release? Cheers, Galder Zamarreño Sr. Software Maintenance Engineer JBoss, a division of Red Hat -----Original Message----- From: Galder Zamarreno Sent: 27 September 2006 18:54 To: Manik Surtani Cc: Brian Stansberry; Vladimir Blagojevic; jbosscache-dev(a)lists.jboss.org Subject: 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? Apart from a customer asking for 776 and 777, which are very non functional fixes and Siemens asking for 761, I haven't see any other customer asking for 1.4.0.SP2. Galder Zamarreño Support Engineer JBoss, a division of Red Hat -----Original Message----- From: Manik Surtani [mailto:manik@jboss.org] Sent: 27 September 2006 12:38 To: Galder Zamarreno Cc: Brian Stansberry; Vladimir Blagojevic; jbosscache-dev(a)lists.jboss.org Subject: 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? 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(a)jboss.org Telephone: +44 7786 702 706 MSN: manik(a)surtani.org Yahoo/AIM/Skype: maniksurtani On 26 Sep 2006, at 14:00, Galder Zamarreno wrote: