Forum OpenACS Improvement Proposals (TIPs): Re: TIP #47: (Implemented) Package Maturity Standards

Collapse
Posted by Malte Sussdorff on
The first part is easy and hopefully someone with a little bit of time can show the maturity level (actually, isnt this shown already)?

Differences between local and CVS version would work if CVS diff was reliable, but somehow I never got it to show me differences when something changed on the server side. Any pointer, so someone can write a page which takes the package-key, looks for the branch TAG in the CVS directory (or for something in the APM which stores what repository to use) and then execute the CVS diff and display the result on the page?

Automatic commit is nice, same is regression test, would be interesting to see it in action.

As for the categories, this requires a TIP but should be implemented in 5.3. It should be a parameter like ā€œ< belongs_to name=dotlrn version=2.2>ā€. No need to restructure the packages directory then.

Additionally, we should have a switch which allows us to mention if a package uninstalls correctly once installed. Though this would probably a good maturity requirement, the conditions in packages and the linking between packages can sometimes prevent this form happening (Iā€™m just thinking about people uninstalling project-manager if it was running in a mixed .LRN/contacts/invoices environment. Cascading will most likely break).