On Thu, Apr 24, 2008 at 2:47 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> Robert Burrell Donkin ha scritto:
>
>
> > there's a lot of code in IMAP-Mailbox. this creates a large barrier to
> > entry both for developers wanting to work on IMAP-Maibox and for
> > developers who want to work on other components.
> >
> > i'd like to think about moving the whole of the IMAP-mailbox code base
> > out of server/trunk and into server/protocols/imap/trunk (say). this
> > move would include the sieve mailet.
> >
>
>  -0. I don't think that disgregation of code will help: we already moved
> mailet outside from james server. We made james server modular. I want to
> see some releases before any other disgregation is done. I'd like to see
> proofs that this road works for real before following it so much.

face facts: JAMES trunk is never going to be released - there just
isn't enough agreement within the developers. so we should aim to
factor out and release what we can agree on.

it's easy to have releases provided that the code released is in the
form of libraries of reasonable size

>  Releases should be the goal, and in the last year we only had 2 jSPF
> releases and nothing else :-((

if you want more releases, step forward

>  Is IMAP-mailbox a standalone library? Has it any use separated from JAMES
> Server code? Is there any developer working on that code lamenting the issue
> of having to work with the whole "server" checked out?

yes (or should be), yes (service, axis, geronimo) and yes (happened a
couple of weeks ago, also noel reported to me that lots of people have
had issues)

> Furhermore at "server" level we already have the TTB structure
> (trunk/tags/branches), I will probably -1 adding a "protocol" folder at the
> same level. IMHO it is against the least surprise principle.

just saves moving stuff down a level. also server/server doesn't make
much sense to me

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to