[jbosscache-dev] Re: Releasing 1.4.0.SP2

[Bela Ban]

+1. We can always go for an SP3 if critical bugs show up.

Manik Surtani wrote:
> Hi all.
>
>
> What is everyones' feel on releasing 1.4.0.SP2?
>
> List of fixes:
>
> ** Bug
>     *  [ JBCACHE-755 ] Potential bug when using (async) replication 
> queue and region based marshalling
>     *  [ JBCACHE-756 ] Marshaller breaks with Strings of length 
> greater than 32767
>     *  [ JBCACHE-760 ] TreeCacheListener in PojoCache gets nodeModify 
> events for invalid objects
>     *  [ JBCACHE-763 ] Transaction rollback does not restore contents 
> of collection of cached collections
>     *  [ JBCACHE-765 ] implementation of equals() in collections is 
> incorrect
>     *  [ JBCACHE-767 ] Fail more silently when setting node versions
>     *  [ 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
>     *  [ JBCACHE-792 ] ChainingCacheLoader method get(Fqn) - 
> unecessary call of the next CacheLoader
>     *  [ JBCACHE-794 ] Eviction Queue hard limit can cause deadlocks
>     *  [ JBCACHE-795 ] listIterator in a cached list throws exception 
> on empty list
>     *  [ JBCACHE-799 ] Bug in RmiDelegatingCacheLoader class
>     *  [ JBCACHE-808 ] Add serialVersionUID to ReplicationException
>
> ** Task
>     *  [ JBCACHE-680 ] TreeCache demo gui to update view instanteously
>     *  [ JBCACHE-761 ] Make connecting the channel and state transfer 
> an atomic part of startup
>     *  [ JBCACHE-793 ] hibernate-recommended-config.xml incorrectly 
> specifies INVALIDATION_SYNC
>     *  [ JBCACHE-798 ] Use ConcurrentHashMap for lock_table
>     *  [ JBCACHE-800 ] Performance problem with TCP & RMI Cache loaders
>
> ** Patch
>     *  [ JBCACHE-766 ] Don't return unnecessary values from 
> _replicate, avoiding need for marshalling
>     *  [ JBCACHE-786 ] errors from "OK" putFailFast replications
>
>
> Specifically, JBCACHE-766, JBCACHE-786, JBCACHE-792 and JBCACHE-800 
> for performance, JBCACHE-761 and JBCACHE-767 for correctness, and some 
> other nasty bugs like JBCACHE-755 have been resolved.  Is there any 
> other reason to hold back this SP?
>
> My original plan was to release 2.0.0.Alpha first, but the 2.0.0 tree 
> is waiting on some config issues being discussed in
>
>     http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92931
>
> 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
>
>
>

-- 
Bela Ban
Lead JGroups / Manager JBoss Clustering Group
JBoss - a division of Red Hat