I reorganized JIRA versions (introduced 2.4 release, marked 2.3.0a2 as
"released" although we never officially released it), updated fix
versions for a few issues and added few tasks for the 2.4 (trunk) release.
So, please open this:
http://issues.apache.org/jira/browse/JAMES?report=com.atlassian.jira.plugin.system.project:roadmap-panel
and tell your opinion on currently scheduled features for 2.3.0 and 2.3.0a3.
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?
Is there anything to add to the 2.3.0a3 ? If nothing urgent to add to
2.3.0a3 imho Noel should prepare a release and we should vote for a
2.3.0a3 release as soon as possible.
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?
Stefano
Stefano Bagnara wrote:
That said, my main request is to know what is the roadmap for 2.3.0
final apart bugfixes.
Imho we should agree on that and understand what we expect from "2.3.0
final release".
I propose that everyone having issues with the 2.3.0a3 release features
should add a JIRA issue and that we may vote and comment the issues so
that we will have a clear roadmap to work in.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
