I disagree. It was a bug, though trivial. And one year ago the behaviour
was like now after the fix (at least at info log level).
And if we find a bug, even not critical, whose fix is trivial, it can
and should be applied even to RC.
I would otherwise yesterday have voted -1 to "[VOTE] James 2.3.0rc1
Release", as it's been two weeks that I said that I was going to test
this weekend in my production system.
And JAMES-515 is not a fix to a bug, simply a cleanup that could
introduce problems to existing customers, and no perceived functional
advantage.
Vincenzo
Stefano Bagnara wrote:
Noel J. Bergman wrote:
Vincenzo Gianferrari Pini
Resolution: Fixed
Changed the log message level to debug when match fails.
Key: JAMES-574
URL: http://issues.apache.org/jira/browse/JAMES-574
Affects Versions: 2.3.0b3, 2.3.0b2, 2.3.0b1, 2.3.0a3, 2.3.0a2,
2.3.0a1, 3.0
Fix For: 2.3.0rc1, 3.0
Uh ... we already voted on and tagged RC1, right? Are we going to
re-roll RC1, or update JIRA to show this in RC2?
--- Noel
IMO this should have not been applied to 2.3 branch.
We are in RC and we should apply only fixes to critical things. This
is not really a bug, only an annoiance.
We should put this stuff in 2.3.1 or 2.4
Otherwise we should change our current 2.3 policy, and we should have
not used the rc tag.
If we start applying similar changes I don't see why we shouldn't
apply http://issues.apache.org/jira/browse/JAMES-515
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
