Steve Brewin wrote:
My preference is to release the a3 anyway: if we never release we'll
always find similar bugs the day we vote for the following release :-(
Personally, I'ld say this is a rather critical bug as aliasing/forwarding is
one of the core usages of James. I don't think we should ever knowingly do a
release that reduces our core functionality.
Cheers
-- Steve
Hi Steve, I would totally agree with you if the bug was present also
with the default (and more used, I thing) jdbc based users repository.
About this specific issue, I am 70% to release anyway (it is an alpha),
30% to include the patch and start the vote for alpha4. My fear is that
everytime people only test the code when we start the vote: I don't want
to start a release vote for each bug until we'll release the final! ;-)
Btw, tomorrow I'll apply the fixes (a+b+c2) to the branch (and trunk, of
course),
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
