Well, you asked for a flood, so how bout...
- Making sure all the core packages have upgrade scripts
- Updating all the core package .info files
- Once the HTML docs are generated, the openacs.org docs should be updated to the new version
- Announcing the new version (bboard, news, etc)
- Merging 4.6 changes back into the head (actually - not sure when this happens)
BTW, is anyone actively working on upgrade scripts right now? If not, I can try. I did a quick look and the following core packages need 'em:
- acs-content-repository
- acs-kernel
- acs-mail
- acs-service-contract
The upgrade scripts all seem trivial except the acs-kernel one. acs-kernel changed some columns from varchar(100) to varchar(1000). We could drop the tables and recreate them, but then all the views and rules based on the tables would also have to be recreated. An article on techdocs.postgresql.org suggests that the only *right* way to change column datatypes is to pg_dump, manually edit the dump file and then pg_reload (which seems like overkill, especially if the user doesn't require the longer field). How should we approach this?
