Hi!
We (the ]po[ core team) are preparing the release of ]project-open[ V5.0 for the next few months. In this release we would like to move to OpenACS 5.8 or 5.9 for PG 9.x compatibility. There are several issues and points at the moment.
- Including ]project-open[ as an "OpenACS Installable Package":
Gustaf asked us some month ago if that's feasible. I like the idea, and we've already worked through half the upgrade scripts of ]po[ "core" and integrated them into the <package>-create.sql scripts. My question now: Would the OpenACS core team want to include the ]po[ packages in the installable package list? How does this work in practical terms? Can you provide use with access to some place where we can upload the packages? We've got nearly 150 packages, maybe there is a bulk upload option?
- Patches to OpenACS:
We had to perform some 3-5 (don't remember exactly anymore) minor patches to OpenACS in the past because of errors. Including ]po[ as an "OpenACS Installable Package" won't work if we don't find a solution for this. Is there still a chance to get these changes in OpenACS 5.9? Or in the next updated version? The problem is that we'd need to test with OpenACS 5.9 to check if these issues persist.
- Upgrading from OpenACS 5.7 to 5.9:
We're trying at the moment, but there seem to be errors. I can't judge whether they are important or not. Did you test the upgrade from 5.7 already?
- AMS required iin OpenACS 5.9?
/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.9.0d3-5.9.0d4.sql says that some function needs ams_object_revisions. I guess there is a missing dependency. But is AMS really a precondition for the CR?
If we don't get this sorted out we'll probably have to release the current release state as ]po[ 4.1 still with PG 8.4 and OpenACs 5.7...
Concerning the main functionality in ]po[ V5.0: We'll include a "Gantt Editor" similar to Microsoft Project etc. written in Sencha ExtJS (HTML5 JavaScript) and a few other Sencha functionality. Checkout http://po41demo.project-open.net/ -> Ben Bigboss -> "Special Machine (2012-16-03)" for example.
Cheers,
Frank