Correct me if I'm wrong but what we're talking about is whether or not to provide an automated hands-off upgrade for this release, or require some manual steps. In either case there will be either scripts or detailed directions.
Originally Dave and I were going to collaborate as mentioned above, with my offering to hack the bootstrap installer to "fix" your installation so the sysadmin can log in and do the rest. That's the primary issue here - if you install 5.0 on top of 4.6.3 you can't log in until an upgrade script is run, but can't run the upgrade script until you log in.
Or you run the script by hand ... then log in and move forward.
In our last OCT meeting I was questioning the wisdom of running this script automatically when rebooting after the files are upgraded ... among other things people may be less likely to fully backup before rebooting thinking they'll have to run the APM upgrades before any changes are made? And if our boot upgrade fails you'd be stuck with an unbootable system perhaps which would really suck ...
So a combination of some manual steps followed by the traditional APM upgrade steps seems safer to me at the moment.
Any comments?
Are there other packages that don't have complete upgrade scripts? We have diddled the way relsegs and groups are managed by the new UI pages slightly between beta and today (bug fix, really) but hopefully people haven't been upgrading their production systems to 5.0 beta expecting stability to be guaranteed?
Am I wrong about this?
I haven't checked to see if Lars provided upgrade scripts to create the new "admin" relseg in all existing subsites but if not we DO need to do that...
