The upgrade process needs to be tested. One way to test would be to create a base 4.6.3 install and update the code to 5.0 then perform an upgrade through the APM. There are existing issues with the authentication package that are being investigated.
There is a forums post and a bug report about the upgrade process:
https://openacs.org/forums/message-view?message_id=143497
https://openacs.org/bugtracker/openacs/bug?bug%5fnumber=1233
I believe Don Baccus is looking into adding code to the acs-bootstrap-installer to detect a potential 5.0 upgrade and run enough of the upgrade to allow the administrator to login to finish the process through the APM.
Another more interesting test would be to upgrade an existing 4.6.3 site with data.
I was specifically working on creating a script that would automatically upgrade from 4.6.3 to 5.0. It is not clear this is a good idea due to the potential for problems with existing data. We don't want to automatically introduce errors into a database.
