> IMHO, what *really* matters for the
> quality of JBoss is the large number
> of users that are using it in a lot
> of different situations, with
> different configurations and different
> beans. A large part of these users
> report when they have problems that
> could be bugs in JBoss, and this
> enables developers to fix things that
> do not work in situations they have
> not even thought about.
> That does not only help to reduce the
> number of bugs in JBoss, but also
> makes JBoss more robust. And IMHO
> robustness is just as important as
> functionality for JBoss.
If developers are not required to write tests for bugs they fix, how can we
be sure that changes down the line won't undo the existing bug fixes?
Anh
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
