[X] +1 | Release MINA 2.0.3
--
Julien Vermillard
Archean Technologies
http://www.archean.fr
signature.asc
Description: PGP signature
+0
Let the release
On Fri, Apr 15, 2011 at 2:30 PM, Julien Vermillard
jvermill...@archean.fr wrote:
[X] +1 | Release MINA 2.0.3
--
Julien Vermillard
Archean Technologies
http://www.archean.fr
+1
On Tue, Apr 12, 2011 at 00:46, Emmanuel Lecharny elecha...@gmail.com wrote:
Ok I restart a new vote for MINA 2.0.3.
The two following bugs have been fixed since the last vote :
http://issues.apache.org/jira/browse/DIRMINA-811
http://issues.apache.org/jira/browse/DIRMINA-827
Bugs
*
Hi guys,
I'm closing the vote, with 5 +1 (Jeff, Niklas, Julien, Guillaume and me)
and one +0 (Ashish).
I'll push the jars and update the site tomorrow, then push the news.
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
On 4/12/11 10:00 AM, Niklas Gustavsson wrote:
On Tue, Apr 12, 2011 at 12:46 AM, Emmanuel Lecharnyelecha...@gmail.com wrote:
[X] +1 | Release MINA 2.0.3
But, I'm missing the distribution packages. Are these available as
binaries somewhere?
yes in
On Tue, Apr 12, 2011 at 10:22 AM, Emmanuel Lécharny
elecha...@apache.org wrote:
yes in
https://repository.apache.org/content/repositories/orgapachemina-078/org/apache/mina/mina-parent/2.0.3/
That's the automated source package that Maven creates for you, it's
not always in the form you want
On 4/12/11 10:26 AM, Niklas Gustavsson wrote:
On Tue, Apr 12, 2011 at 10:22 AM, Emmanuel Lécharny
elecha...@apache.org wrote:
yes in
https://repository.apache.org/content/repositories/orgapachemina-078/org/apache/mina/mina-parent/2.0.3/
That's the automated source package that Maven creates
Oopps, sent to the wrong list.
On 4/12/11 10:47 AM, Niklas Gustavsson wrote:
On Tue, Apr 12, 2011 at 10:39 AM, Emmanuel Lécharny
elecha...@apache.org wrote:
Although, we don't distribute a binary package, containing all the jars :
it's not useful, as nobody includes all the jars in its
On 4/12/11 10:47 AM, Niklas Gustavsson wrote:
PS : I can put the dsitribution content on people.apache.org/~elecharny, but
is this necessary ?
I would like that, or in repository.a.o.
Ok, done :
http://people.apache.org/~elecharny/
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
On Tue, Apr 12, 2011 at 11:13 AM, Emmanuel Lécharny
elecha...@apache.org wrote:
Ok, done :
http://people.apache.org/~elecharny/
Thanks, look good.
/niklas
[X] +1 | Release MINA 2.0.3
--
Julien Vermillard
Archean Technologies
http://www.archean.fr
signature.asc
Description: PGP signature
Hi guys,
I don't think it's a bad news, but I have to cancel the release vote :
we have had two major issues discovered lately, DIRMINA-811 and DIRMINA-827.
Both have a fix, and I'll cut a new release tomorrow.
I'll keep you informed asap.
Thanks !
--
Regards,
Cordialement,
Emmanuel
Ok I restart a new vote for MINA 2.0.3.
The two following bugs have been fixed since the last vote :
http://issues.apache.org/jira/browse/DIRMINA-811
http://issues.apache.org/jira/browse/DIRMINA-827
Bugs
* [DIRMINA-627 https://issues.apache.org/jira/browse/DIRMINA-627] -
+1
Jeff
On Apr 11, 2011, at 4:46 PM, Emmanuel Lecharny wrote:
Ok I restart a new vote for MINA 2.0.3.
The two following bugs have been fixed since the last vote :
http://issues.apache.org/jira/browse/DIRMINA-811
http://issues.apache.org/jira/browse/DIRMINA-827
Bugs
* [DIRMINA-627
+0
Not in a position to spend time with release. would luv to see 2.0.3 out.
Thanks Emm for taking all the pain :)
On Sat, Apr 9, 2011 at 9:55 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
This is a bug fix release. The most important issue was the 100% CPU issue :
we have removed the
This is a bug fix release. The most important issue was the 100% CPU
issue : we have removed the workaround in 2.0.1, and it seems that it
was a wrong move. The workaround has been added back.
The fixed issues are :
Bug
* [DIRMINA-627 https://issues.apache.org/jira/browse/DIRMINA-627]
+1
Jeff
On Apr 9, 2011, at 10:25 AM, Emmanuel Lecharny wrote:
This is a bug fix release. The most important issue was the 100% CPU issue :
we have removed the workaround in 2.0.1, and it seems that it was a wrong
move. The workaround has been added back.
The fixed issues are :
17 matches
Mail list logo