No, it isn't dead. I've been consumed on some other things, and no one else
has been merging changes into MAIN.
In some cases, we've had patches submitted that there done in such manner as
to be more work (new files should be submitted as files, not embedded in the
diff), and I haven't had time. Vincenzo has been on vacation, and others
have been consumed.
HOWEVER, getting to one of your points, since v2.2 is not v2.1, I would like
to get it into sync with the latest Avalon Release, and make that part of
the v2.2.0 Release.
My proposal has been that we bring v2.2 up to date with the latest Avalon
code, make ONLY such changes to the Mailet API that we really are SURE that
we want to keep, put the remainder in an experimental branch, and merge v2.2
back into MAIN. If I recall correctly, the only desired differences between
v2.2 are the Avalon changes and those experimental Mailet API changes. I
think we'd like to keep all of the good work that was done on the build
process in MAIN, rather than revert to the older approach in the v2 branch.
Doing this would reduce the maintenance overhead, give me a clean base to
start adding the JNDI code, and make it a darned sight easier to keep the
Web-site up to date.
--- Noel
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 17:34
To: James Developers List
Subject: is 3.0 a dead branch
I'm currently running an instance of James based on CVS HEAD. Looking
at some of the recent comments on the dev and user lists it appears that
updates are being applied to 2.1/2.2 and that HEAD is now not really
HEAD at all. Should I be dropping 3.0a1 in favour of 2.2 (which I'm not
too keen on since 3.0a1 is totally in sync with all of the latest avalon
releases).
Any comments and/or suggestions about appropriate direction appreciated.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
