Forum OpenACS Development: Response to 4.6 release checklist

Collapse
Posted by Jon Griffin on
I don't think requiring people to read cvs logs is a real way to document changes in the core of an app. I of course could have read the logs, but I shouldn't have to.

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.