Re: upgrade to 3.2.1

Am 17.12.2014 um 00:26 schrieb Lee Howard:
> Back in July I asked about upgrading to 3.1.16 and was counseled to wait
> for 3.1.17.  So, I waited, but I never upgraded to 3.1.17.
>
> I see that 3.2.1 is released... at least partially.
>
> I need to upgrade to avoid dbmail-pop3d problems in 3.0.2 that I believe
> were resolved long ago.  Do I have a green light from the developers on
> using 3.2.1?
>
>  From looking at the UPGRADING document, it appears that the DB schema
> auto-updates.  So, I don't need to run anything in sql/mysql to update.
> Correct?

don't get me wrong: nonody but you can give a green light and as for all 
major upgrades you need to *test* it before put it in production

so mirror the complete database folder on a test installation and try 
the migration - that's the only way to find out if there are migration 
issues in your case

it don't help even much if 1000 people confirm a upgrade without any 
issue and with your data the scheme migration stops in the middle with a 
SQL error (been there due migration to 3.0 and it needed a lot of 
cleanups after i was save to migrate the prouction server removing 
duplicate records and garbage before)

_______________________________________________
Dbmail-dev mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSQw+YACgkQhmBjz394AnkgRwCggOj88PPnXFBXsEh8XuqRKLkx
T48AnRyi2dd3+QlqobdtO3lKsKg+EzbN
=/EXc
-----END PGP SIGNATURE-----