Change Details

Beat on our custom modules, especially. Rolling back an upgrade would be a big effing deal, so test thoroughly and realistically. Iterate generously. Consider installing a safety mechanism ahead of time, such as entity auditing. This would give us the ability to replay some of the lost changes, if we do have to roll back. Time the upgrade itself, and note the load it puts on the database.

Some notes here: https://etherpad.wikimedia.org/p/Civi_4.6_staging_deployment Beat on our custom modules and integration with other subsystems, especially. Rolling back an upgrade would be a big effing deal, so test thoroughly and realistically. Iterate generously. Consider installing a safety mechanism ahead of time, such as entity auditing. This would give us the ability to replay some of the lost changes, if we do have to roll back. Time the upgrade itself, and note the load it puts on the database.

Some notes here: https://etherpad.wikimedia.org/p/Civi_4.6_staging_deployment Beat on our custom modules and integration with other subsystems, especially. Rolling back an upgrade would be a big effing deal, so test thoroughly and realistically. Iterate generously. Consider installing a safety mechanism ahead of time, such as entity auditing. This would give us the ability to replay some of the lost changes, if we do have to roll back. Time the upgrade itself, and note the load it puts on the database.