> Marc Chamberlin wrote:
>
> These may be more of the type of questions for some of the James
> developers to answer, but I thought I would start with the James users
> because they may have faced some of these issue also.... (And
> hopefully a few of the James developers are lurking ;-) on this group
> as well. )
Lurking happens ... :-)
> I have installed the released version of James, version 1.2.1 and have
> configured it to handle a few users, some list servers, and a couple
> of custom mailets.
Hurrah!
> Now, lets say I want to upgrade to one of the
> latest nightly builds, what procedures should I follow in order to
> preserve my existing configuration? Can I simply unzip the download
> zip files in place over the top of my existing James directories, or
> should I unzip to a separate directory? If I should do the latter,
> then what files from my previous James installation should I copy over
> into my new directories? I can certainly figure out a few of the more
> obvious ones, but am not sure I could guess at everything that I would
> need to do... Are there any guidelines published? ;-)
In general, there aren't any guidelines for upgrading to a nightly
build.
Not least because it is a moving target until we get close to a release.
In the case of James, there are major infrastructure changes reflecting
changes in the underlying Avalon framework.
You should definitely test nightly builds separately from any existing
installation.
Also note that the config files have changed format (and number) so you
can't copy them across. But they are hopefully easier to use, now.
Once we are close to a release if someone wants to write and contribute
an upgrader, that would be great.
>
> A related question, is there any plans to wrap the James installation
> process inside some installation application, such as InstallShield
> for us handicapped Windows slaves, so as to make the installation of
> upgrades somewhat painless?
>
Again, once we are close to a release, if a Windows guru wants to write
and contribute an instaler that would be great. (Assuming licence
compatability with Apache)
>
> And a third question - Is there any expected time frame for the next
> release of James? I am mostly just curious and trying to plan ahead a
> bit... ;-)
Damn good question!
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
