In upgrade41.html, we introduced a "warning" section about packages
with unusually traumatic upgrades.  In the 4.0 -> 4.1 upgrade,
(and for 4.3 -> 4.4, apparently) postgresql required a database dump
before the upgrade and a restore afterwards, if one neglected to do
this, they would be hurting after installing the new version.

It's upgrade43.html time again, and I need to know if there are any
packages worthy of a upgrade warnings for 4.2 -> 4.3

The criteria I would like to use is this:
  1) The upgrade is more traumatic than typical (for example,
     requiring PRE-upgrade actions)
  2) the package is in moderately wide-spread use.

For 4.0->4.1, the postgresql advisory was this:

* Postgresql: you must dump your database before upgrade and restore it after

nice, neat, one-line.

Please submit any suggestions for these to me.  Providing the nice,
neat, one-line summary would be great (I'm NOT good at nice, neat, OR
one-line!), and if you feel it needed, justify it to me. :)


Nick.

Reply via email to