Hi,
my VOTE:
1) +0
2) +0.6
3) +0.4
4) -0
bye
Norman
Stefano Bagnara schrieb:
Hi all,
4 days ago we released James 2.3.0RC4 and we already collected 3 bugs
and fixed them:
JAMES-625 - an empty mbox will cause an error at pop3 login
https://issues.apache.org/jira/browse/JAMES-625
Critical, but only when using MBoxFileRepository (I expect other
similar bugs in less used components)
JAMES-644 - FileRegexMatcher possibly leaks minor memory on startup
https://issues.apache.org/jira/browse/JAMES-644
A minor issue: a single file descriptor is kept busy during all the
james life.
JAMES-649 - error "OutOfMemoryError: JAVA HEAP SPACE" in connections
log file when doing a POP TOP for 4000 messages
https://issues.apache.org/jira/browse/JAMES-649
Well, the fix for this is an optimisation: we now avoid to parse the
message in pop3 top calls and try to stream it directly.
---
Now we have a choice for the next step:
1) start a vote to release 2.3.0rc4 as 2.3.0 final
2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
4) wait few days more.
I have not a strong opinion on this, because I'm already focused on
our trunk.
My "votes" are:
1) +0.6 I would at least remove the mbox comment in config.xml
2) -0 We never followed this workflow
3) +0.4 Apply all of them
4) -0 I don't like to wait ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!EXCUBATOR:1,45269bda53078579914879!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
