On Sun, Feb 21, 2010 at 4:23 PM, Emmanuel Lécharny wrote:
> Ok, guys,
>
> sorry for my overreaction...
>
> Sure we have to check what's going on with the builds.
>
> If we look at the build history, we see that we don't have that many
> failures. The problem is that those failures seems to be time
On Sun, Feb 21, 2010 at 1:23 PM, Julien Vermillard
wrote:
> Sounds like you are pissed now, try to breath ;)
> I'm agree for releasing 2.0 now.
+1
/niklas
Sounds like you are pissed now, try to breath ;)
I'm agree for releasing 2.0 now.
Julien
Le Sun, 21 Feb 2010 11:53:28 +0100,
Emmanuel Lécharny a écrit :
> Ok, guys,
>
> sorry for my overreaction...
>
> Sure we have to check what's going on with the builds.
>
> If we look at the build histor
What I want to say is : get this bloddy 2.0 out, and let's bury it. It's
dead code, it's a cancer we can't fix. Any time we spend on it is a
waste, and slow down our work on MINA 3.0.
We have some issues like DIRMINA-764, but it can be worked around on the
client side, and can't be fixed on the
Ok, guys,
sorry for my overreaction...
Sure we have to check what's going on with the builds.
If we look at the build history, we see that we don't have that many
failures. The problem is that those failures seems to be time-dependent.
The JDK 1.6/Windows build are also in constant failure, a
