[Mailman-Developers] installing 2.1b1 on top of 2.0.8

[Mentor Cana]

Thanks for the e-mail. I have already installed 2.1b1 in a separate
location (both version 2.0.8 and 2.1b1 working just fine). However, my
current 2.1b1 installation is a test instalation only. That's where I test
my CVSs before installing in the production location.

However, my current 2.1b1 was an incremental upgrade from the CVS every few
days, starting with pre 2.1a4. So, hopefully going directly from 2.0.8 to
2.1b1 will not be a problem. Yeh, we have to be carefull about all the
small things  you have listed below. And hopefully, after I do all of that
things will work! :) Judging from previous experience  I don't anticipate
any problems, but, it does not hurt to ask if someone has already gone
through that path....

I'll send an e-mail once I'm done... :)

later,
Mentor

On Mon, 18 Mar 2002, at 12:29 -0500, Ron Jarrell wrote:
 > At 12:17 PM 3/18/02 -0500, you wrote:
 >
 > >Has anyone installed 2.1b1 on top of 2.0.8? I'm tempted to do so and I
 > >would appreciate any first hand experience.
 > >
 > >Is this recommended or is it prefered that we install 2.1b1 in another
 > >location and than move the 2.0.8 lists to the 2.1b1 location?
 >
 > It ought to work just fine.  I haven't gone and done my prod machine
 > (this week) but my test machine was getting a never ending stream of
 > "Oh look - 6 more commits came in from 'Commit Happy Barry' :-) while
 > I was doing the install for the last 14." and if it compiled at all, it installed
 > cleanly...
 >
 > Do read the docs carefully - a lot of things have changed; before putting the
 > service back in production you'll need to create the site mailing list, potentially
 > regenerate all your email aliases (there's a program to do so if you aren't
 > using an auto-routing mailer), and change your crontab, just off the top of my
 > head.  Oh yea, and go over mm_cfg with a fine tooth comb, cause a lot of
 > stuff changed in there and in Defaults.   You'll also need, although not
 > necessarily immediately, an appropriate script to start the persistent
 > qrunners (not out of cron anymore), and if you've been customizing list
 > pages, you'll need some serious repair work there.
 >
 >