james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrell DeBoer" <li...@bigdaz.com>
Subject Re: Nearly ready for release
Date Fri, 28 Sep 2001 03:05:50 GMT
G'day

Great work, Serge (and everyone who helped out). Sorry I haven't been of
much help - just about through my current work bottleneck, and I should find
some more time...

I would suggest releasing alpha1 as is, and leaving these mods for alpha2.
IMHO, we could benefit from having several alphas prior to bringing out a
beta release. This would give us a chance to work on some useability issues
and doco, while (hopefully) adding a few more users who in turn will report
more bugs.

A question: What's the story with version compatibility between alpha
releases (and the subsequent betas)? Will it be OK to change the config file
format (eg to simplify switching POP/SMTP/IMAP on/off) between alpha
releases, even if this means more work to upgrade from one alpha to the
next? My assumption was that alpha releases could break compatibility,
whereas making upgrade automatic was more important between beta releases.

ciao
Daz

----- Original Message -----
From: "Serge Knystautas" <sergek@lokitech.com>
To: <james-dev@jakarta.apache.org>
Sent: Friday, September 28, 2001 7:26 AM
Subject: Nearly ready for release


> I got the outstanding patches applied, changelog done, and removed the
last
> of the Town code.
>
> Outstanding things I have left to do before release...
> 1. The listserv classes
> I want to simplify these by just having a single GenericListserv class
> rather than this overly complicated listserv and listserv manager class
(and
> CommandForListserv and other funny matchers).  Also I want to rewrite the
> database implementation since I just deleted the town implementation this
> afternoon (as it was the only thing stopping me from deleting town.jar).
>
> 2. Add Regex matchers
> I've changed my mind about how to do these cleanly. :)  I may still stick
> them in a different package to keep the directory listings smaller, but my
> planned convention is "HostIs" is the standard matcher, and "HostRegex" is
> the regular expression matcher.  Got some matchers Oki sent me, plus some
of
> my own I'll add.
>
> 3. User documentation
> We really should write something up at some point.  At least a bunch of
> simple howto's.  ideas to do...
> a. how to setup user accounts for pop3
> b. how to setup a database for message storage
> c. how to setup a database for user accounts
> d. how to write a mailet
> etc...
>
> 4. Log files getting wiped
> This seems like a "feature" of the new Avalon, but every time you start
> James, all the log files are wiped.  If anybody knows more about this,
> that'd be great, otherwise I'll start digging in shortly.
>
> I think that's about it... I'll start some testing soon and then update
the
> website for the 2.0a1 release.  I figure we'll the user/dev listserv know
> about this, find the problems we forgot to patch, and then maybe for the
a2
> or b1 release announce to the rest of the world.  If anybody else sees a
> patch that wasn't applied or spots another bug, please let me know.
Thanks!
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org


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


Mime
View raw message