JWM wrote:
Stefano,
I am currently running 2.2.0a17. I have no problem installing 2.3.0a1 and
testing. But can you tell me if I have to make changes to my config file in
order to upgrade? If so, is it massive? I seem to remember that I had
significant amount of changes required when I moved up to where I am now.
I'd love to move up and test it (and hopefully solve the problem). But I
don't have the bandwidth to do a major migration. Will everything still
work as-is on the new version?
There are many changes in configuration files:
http://wiki.apache.org/james/JamesV2
2.3.0a1 is ALPHA code so it is not stable: you probably want to test it
only to tell us wether the problem is solved or not so it will be
included in the next stable release.
The good news is that James 2.3-x is fully storage compatible with 2.2.0
so, to move from 2.2.0 to 2.3.0 and back you only need to change the xml
files and the phoenix distribution but you can keep the same identical
db / file store.
So, don't put 2.3.0a1 in production right now, but you probably want to
test it and let us know if the dns problem is solved and if the
2.2.0-2.3.0 upgrade path seems to be easy or if you find any problem
working on it.
You 2.2.0a17 is a "standard" distribution or have you added any
matcher/mailet/custom code to it?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
