james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: What's In 3.0? [WAS Re: [VOTE] next-major from trunk will be 3.0]
Date Tue, 07 Aug 2007 12:53:42 GMT
On 8/7/07, Stefano Bagnara <apache@bago.org> wrote:
> Robert Burrell Donkin ha scritto:


> > feedback from users should be very useful in deciding the best approach
> Will we be able to support our users on every implementation we have in
> trunk? I personally have limited knowledge in some handlerapi code and
> with the imap modules.
> IMHO we should at least care to release as default something that we are
> ready to support and for which someone will reply to user questions.

a milestone is just a preview. we're not committed to support anything.

> > the handlerapi isn't really my area so someone else would need to
> > volunteer push this forward
> I have knowledge of the experimental handlerapi code we release in
> 2.3.x. The we had 2 branches, one sandbox and trunk evolving with
> different solutions.
> I know what's in the handlerapi-experiment sandbox and I can tell it is
> a big refactoring involving changes in the core and in most modules so
> to refactoring of the current code to support a SEDA pattern, so maybe
> we should ignore it for 3.0M1.
> I don't know much of the trunk vs 2.3 and the 2 branches: maybe Noel or
> Norman can help us identifying what's what and what do they think we
> should include in M1.
> What I would like to avoid is releasing one more different experimental
> handlerapi with the knowledge we will change it again in M2 and then
> again in M3 and so on. In this case I would prefer to revamp 2.3 code
> for handlerapi and keep that module as "default" for a while (while we
> better understand what can be done there).

sounds ok to me but i'm not really up on the handlerapi code


- robert

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message