I finished merging back the bugfixes.
Since the last "update" we added this:
http://issues.apache.org/jira/browse/JAMES-489
http://issues.apache.org/jira/browse/JAMES-504
http://issues.apache.org/jira/browse/JAMES-503
http://issues.apache.org/jira/browse/JAMES-501
Btw, more minor bug fixes will probably come later, but we should put
out a new release (alpha, beta or release candidate, I don't care)
I'm impatient to cast my "+1" to the next release vote ;-)
Stefano
Noel J. Bergman wrote:
Stefano Bagnara wrote:
I reorganized JIRA versions (introduced 2.4 release,
marked 2.3.0a2 as "released" although we never
officially released it)
Thank you. :-) More on the latter below.
I think that all of the 2.3.0 features but JAMES-432 and JAMES-496
could be moved to 2.4 or 3.0: do you agree?
Is there anything to add to the 2.3.0 roadmap?
Actually, I was going to say that I'm fairly happy with what we have, once
we have finished testing.
If nothing urgent to add to 2.3.0a3 imho Noel should prepare a release
I can do so this week. Even if I have a problem with the build server, I
can do it on my personal build VM.
Should things like JAMES-489 and my fix to the locking/unlocking of the
outgoing spool (found and fixed during the JAMES-491 refactoring) be
merged and included in 2.3.0 roadmap or you prefer to keep them only for
the 2.4 release?
Yes for JAMES-489, and I was going to ask you the same question about the
locking changes. What's your view? If you're confident in the fix, I'd say
that we should put it into 2.3.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
