Forum OpenACS Development: 4.6 release checklist
- Update major/minor versions in DocBook docs.
- Update readme.txt
- Regenerate .html docs from DocBook
- Make sure release notes are up to date
- Make sure the checkout is clean and the file protections are correct
- Make sure you can bootstrap on postgresql and oracle
- Make sure there are not excessive notice/warning messages generated when running a server.
- Tag CVS
- create dist files (tarball, etc)
- add version to SDM
will happen soon :)
I will make sure Janine gets a summary for the permanent record.
- 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)
I noticed that in acs-kernel also and it does cause things to choke.
I would like to know who changed this and why to chastise them publically for breaking the kernel without even a note.
Again, please don't change the kernel without a good reason and posting it on the board for public scrutiny.
It's all there in black and white in the cvs log.
revision 1.15 date: 2002/09/16 21:52:42; author: jeffd; state: Exp; lines: +3 -3 increase field sizes (from sloan)I think people can upgrade happily from 4.5 to 4.6 (or could if there were more upgrade scripts) without changing these field widths and I am curious why you think it causes things to choke Jon.
In the future I will try to post something to the bboards before I make a change like that.
The break occurs because in PG as Vinod pointed out just altering column widths screws up other stuff. I am not sure that my upgrade problem was solely because of this but I couldn't upgrade a 4.5 install to 4.6 and ended up doing the dropdb redo it all from scratch. Of course this was the day of the beta release and some scripts didn't exist at all.
Just please discuss these changes before they are made as sloanspace doesn't run the openacs project. And while they may have good reasons for doing this some discussion should have taken place publically. If no one can upgrade because of a multitude of problems (no scripts, difficult to change functionality, etc), then our audience will just get smaller.
be on an OpenACS release checklist beyond what Vinod and I covered?
First cvs export -r oacs-4-6-3-final openacs-4 to a temporary directory.
Then I cp acs-core-docs /web/openacs.org/www/doc/opeancs-4-6-3.
Finally I add a link in /web/openacs.org/www/doc/index.adp to the new documentation.
I think we can improve this process when we get openacs.org running as a branch of the openacs repostiory. We can more easily keep the code base up to date, and the acs-core-docs installed on openacs.org will be the latest version.
Also as part of the release process it might be a good test to update openacs.org with the final release code.