I would appreciate if package maintainers could report the status and any open items that they are working on. As far as I can say we have one more month to address them before beta. If there's no report for a package, that package will remain unclaimed in the project status page that I'm preparing until someone comes forward and takes responsibility.
If anyone disagrees with the time framework for releasing 4.6 or any posted open items, please say so in your post but let us start another thread to discuss it so that this thread is only used for feedback.
Only report if your package is in the OpenACS CVS tree. I'm asking people to post here since it would be difficult for me to verify who maintains what. I'm sure Don and others will jump and say if something does not look right.
I'm gonna post more information about upgrade scripts and other things we should take into consideration on a follow-up message.
Here's an example of the requested info for the packages I maintain For example, here are the packages that I maintain:
- ACS Service Contracts (a-s-c)
- an alternative interface for OpenACS to work with tdom
- xml-based version of A-S-C
Note 2: No upgrade scripts are required.
Note 3: I have a long TODO list of long term goals but we can post those after we're done with this thread. None of those goals is planned for 4.6. A TODO list for OpenACS shall be used to gather information for such long term goals.
Note 4: In the past I've also ported to postgresql the latest version of ACS Workflow based on Dan's port of an earlier version. Given the fact that the designer of the package (Lars) have since join us, I think it's up to him if he wants maintain both the oracle and the postgresql version of the package.
Note 5: Like many others I've had my share of work on the OpenACS core but I'll let Don address what would happen with the core.
I think that's all for now and I look forward for your comments.