|
Content-Transfer-Encoding: |
7bit |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Thu, 9 Jan 2003 22:49:08 -0500 |
Content-Type: |
text/plain; charset=us-ascii; format=flowed |
MIME-Version: |
1.0 |
Reply-To: |
|
> Liam Kelly <[log in to unmask]> wrote, in part:
>>...Personally, I would just make a copy of your current
>>~/listserv directory, run the standard 'make update' during off-hours, do
>>some testing, and roll back to the copy if you don't like the result. It
>>would almost certainly be less headache...
In addition to this, I download and study the template changes before
making the change. Many tailorings are trivial; many are not. You may
want to give your list owners a heads-up before or after the actual
install. You certainly want to have your revised site templates ready
when you install the update, or at least understand the consequences of
not having *your* template updates ready. I try to give my high-profile
-list owners a heads-up.
This is certainly the biggest headache of LISTSERV updates ... LSoft
seems to have a long history of otherwise painless update installation
for the majority of sites. That's certainly been the case for us.
cheers, wayne
--
Wayne T. Smith -- [log in to unmask] -- Systems Software Analyst
University of Maine System (UNET)
|
|
|