Upgrading cyrus

[Benjamin Seidenberg]

On 09/10/2010 01:18 PM, Patrick Goetz wrote:
> On 08/14/2010 08:12 PM, Benjamin Seidenberg wrote:
>> The main thing that has yet to be done is work on an automated upgrade
>> path from existing 2.2 installations to the 2.3 packages. If you want to
>> test these packages, please let us know about how your upgrade process
>> went - what worked, what didn't and how you fixed any problems you
>> encountered.
>>
>
> > On 09/01/2010 03:20 PM, Patrick Goetz wrote:
> >> I'm guessing that most people who are upgrading a mail server are
> >> upgrading the hardware, too.
> >
> > Please provide a basis for that assertation. I think that that's
> > probably true for large installations, but for many small
> > businesses/organizations it is not.
>
>
> Hi -
>
> I never responded to this. Although I *think* most people will want to
> upgrade their hardware at the same time that they upgrade their mail
> server software (hardware is cheap after all, and labor is expensive)
> I suppose I could be wrong about this.  But in any case I didn't think
> about the case of murder installs.

That may be true for large organizations, but misses TONS of use cases,
from individuals with personal servers to non-profits to schools to
places where admins can choose to spend their time more easily than they
can requisition new hardware to.... Additionally, it fails to take in to
account a variety of reasons for upgrading - tracking security updates,
wanting new features, etc. Also, I think that doing a message sync via
imap is significantly more complex for a user than using a pre-written
script to update their database.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20100912/f878ae4e/attachment.pgp>