This news change a little my ideas and make it more "strong":
> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
+1 after having removed MBox class at least from the config (I don't
care to remove the file, my vote does not change in this regard)
> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
-1 too much changes to make a final relase without a further RC
> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+0.5 including all fixes but I would anyway remove the comments about
MBoxMailRepository from the config.xml (it is for clear an untested
class so even if we fix this issue it could have many other issues and I
don't want them to block the release)
> 4) wait few days more.
-0 as before
Stefano
Norman Maurer wrote:
Hi,
i must add some more infos. After testing more the MBoxMailRepository i
again found a new Bug.
See: http://issues.apache.org/jira/browse/JAMES-655
So there are 4 ways to solve this isssues for 2.3
1) Fix in 2.3 branch
+0.8
2) Remove it from 2.3 branch
+1
3) Hide configuration from 2.3
+0.2
4) Fix not in 2.3
-1
Bye
Norman
Bernd Fondermann schrieb:
On 10/6/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Now we have a choice for the next step:
1) start a vote to release 2.3.0rc4 as 2.3.0 final
+1
2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
-1
3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+0
4) wait few days more.
-0
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
