Well, there are occasional simple database changes that can be done with db-update... For those, I'd just run cvsreport itself ( not with -sync ) and if update-db-general.pl, then you've got a simple changes.
db-update should be ran every update, anyway.
Any more complicated changes will be as kareila said.
It may be safest to wait a week or two after the code push before updating to the latest tag ( and stay one push behind until then ), so we can catch any lingering issues ( we are already on 1.0.1 due to some issues from the push )
For a production site, to minimize surprises:
You are going to want to have *all* of your configuration files copied into cvs/<dir I had you create>/etc, and compare the diffs between versions to see if there are any important changes.
You should probably run cvsreport first w/o args before -sync, to make sure you know what is changing.
no subject
For those, I'd just run cvsreport itself ( not with -sync ) and if update-db-general.pl, then you've got a simple changes.
db-update should be ran every update, anyway.
Any more complicated changes will be as
It may be safest to wait a week or two after the code push before updating to the latest tag ( and stay one push behind until then ), so we can catch any lingering issues ( we are already on 1.0.1 due to some issues from the push )
For a production site, to minimize surprises: