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
