[mythtv-users] staging an upgrade 0.20 -> 0.23

[Ross Camm]

with a two young boys who demand zero myth downtime, i am proposing the
following ( lengthy ) staged major upgrade from 0.20 to 0.23....please
tell me if it is completely insane  ;)

Environment:

dedicated backend on debian etch with mythbackend 0.20 installed using deb
packages, and mythtv 0.23 installed from src under /usr/local

MythTV Version   : 0.23.1
MythTV Branch    : tags/release-0-23-1
Network Protocol : 23056
Library API      : 0.23.1.201000710-1
QT Version       : 4.4.3


dedicated various ubuntu 10.4 frontends with mythfrontend 0.20 installed
from src under /usr/local ( opposite of backend above) and mythtv 0.23
installed using ubuntu deb packages

MythTV Version   : 24158
MythTV Branch    : branches/release-0-23-fixes
Network Protocol : 56
Library API      : 0.23.20100314-1
QT Version       : 4.6.2


Proposal:

I am preparing for major downtime due to the difference in the versions,
0.20 to 0.23.1, and the impact this may have current SLA's !...being a
single parent and all ! <violins>

I am looking at:

1. backing up the current mythconverg 0.20 database using
mythconverg_restore.pl...latest version 1.0.10

2. restoring this to a different database..lets call it mythconverge23, on
the same backend on the same mysql server