On Tue, Sep 14, 2010 at 1:23 AM, Emmanuel Lécharny <[email protected]> wrote:
>  On 9/13/10 11:43 PM, Maarten Bosteels wrote:
> Then 30 minutes later, it passes. I have no idea why it behaves this
> way, but this is systematic, and not only for MINA, but also for Vysper,
> FtpServer and so on.

This is not true, at least not for Vysper and FtpServer. There are two
types of issues we've seen in Hudson in these two projects:
* Failed builds due to Hudson stability problems. These are easily
recognized since the build will fail with a Hudson error rather then a
build error. Typical example is a borked connection to a Hudson slave.
For Vysper and FtpServer I try to clean these from Hudson history when
they happen.
* Failed builds due to build problems, recognized problems coming from
the build, typically test failures. This seems to be the case with
MINA on Windows at the moment.

> Well, I think we should release a 2.0.0, and then fix issues as fast as we
> can, releasing a 2.0.1 if needed. IMO, we have waited way too much for this
> 2.0.0

Agreed. I think we could aim for a 2.0.1 within a month. But, of
course I don't do much work on MINA itself so view this as some random
user's opinion :-)

/niklas

Reply via email to