What about releasing a 2.0-RC2/2.0.0 ?

2010-01-12 Thread Emmanuel Lecharny 

We have fixed some important issues lately in 2.0-RC1 :
DIRMINA-749 : We cannot anymore inject more than one CODEC in the chain.
DIRMINA-678 : NioProcessor 100% CPU usage on Linux (epoll selector bug)
DIRMINA-650 : Mina server does not recieve all data sent by client using 
SSLSocketFactory


Isn't it time for a new release ? Should we call it 2.0.0 ?

--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com

Re: What about releasing a 2.0-RC2/2.0.0 ?

2010-01-12 Thread Jeff Genender 

+1

Jeff

On Jan 12, 2010, at 10:02 AM, Emmanuel Lecharny wrote:


We have fixed some important issues lately in 2.0-RC1 :
DIRMINA-749 : We cannot anymore inject more than one CODEC in the  
chain.
DIRMINA-678 : NioProcessor 100% CPU usage on Linux (epoll selector  
bug)
DIRMINA-650 : Mina server does not recieve all data sent by client  
using SSLSocketFactory


Isn't it time for a new release ? Should we call it 2.0.0 ?

--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com

Re: What about releasing a 2.0-RC2/2.0.0 ?

2010-01-12 Thread Julien Vermillard 
Le Tue, 12 Jan 2010 18:02:41 +0100,
Emmanuel Lecharny elecha...@gmail.com a écrit :

 We have fixed some important issues lately in 2.0-RC1 :
 DIRMINA-749 : We cannot anymore inject more than one CODEC in the
 chain. DIRMINA-678 : NioProcessor 100% CPU usage on Linux (epoll
 selector bug) DIRMINA-650 : Mina server does not recieve all data
 sent by client using SSLSocketFactory
 
 Isn't it time for a new release ? Should we call it 2.0.0 ?
 

+1


-- 
Julien Vermillard

Archean Technologies
http://www.archean.fr


signature.asc
Description: PGP signature

Re : What about releasing a 2.0-RC2/2.0.0 ?

2010-01-12 Thread Edouard De Oliveira 
I'm sorry but after examining the remaining bug list i think 
https://issues..apache.org/jira/browse/DIRMINA-711 must be fixed before issuing 
2.0.0 the framework can't fail because we just add some logs otherwise we must 
make this mdc feature optionnal  

I'm really in favor of releasing 2.0.0 and creating dynamicity in the community 
let just fix 711

-1 (for a short moment i hope)
 Cordialement, Regards,
-Edouard De Oliveira-
Blog: http://tedorgwp.free.fr
WebSite: http://tedorg.free.fr/en/main.php



- Message d'origine 
De : Julien Vermillard jvermill...@archean.fr
À : dev@mina.apache.org
Envoyé le : Mar 12 Janvier 2010, 18 h 35 min 01 s
Objet : Re: What about releasing a 2.0-RC2/2.0.0 ?

Le Tue, 12 Jan 2010 18:02:41 +0100,
Emmanuel Lecharny elecha...@gmail.com a écrit :

 We have fixed some important issues lately in 2.0-RC1 :
 DIRMINA-749 : We cannot anymore inject more than one CODEC in the
 chain. DIRMINA-678 : NioProcessor 100% CPU usage on Linux (epoll
 selector bug) DIRMINA-650 : Mina server does not recieve all data
 sent by client using SSLSocketFactory
 
 Isn't it time for a new release ? Should we call it 2.0.0 ?
 

+1


-- 
Julien Vermillard

Archean Technologies
http://www.archean.fr

Re: What about releasing a 2.0-RC2/2.0.0 ?

2010-01-12 Thread Ashish 
+1

On Tue, Jan 12, 2010 at 11:05 PM, Julien Vermillard
jvermill...@archean.fr wrote:
 Le Tue, 12 Jan 2010 18:02:41 +0100,
 Emmanuel Lecharny elecha...@gmail.com a écrit :

 We have fixed some important issues lately in 2.0-RC1 :
 DIRMINA-749 : We cannot anymore inject more than one CODEC in the
 chain. DIRMINA-678 : NioProcessor 100% CPU usage on Linux (epoll
 selector bug) DIRMINA-650 : Mina server does not recieve all data
 sent by client using SSLSocketFactory

 Isn't it time for a new release ? Should we call it 2.0.0 ?


 +1


 --
 Julien Vermillard

 Archean Technologies
 http://www.archean.fr




-- 
thanks
ashish

Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal