Ahhh, yes..... Apologies about the slight delay. Other more important things seem to keep getting in the way 😉.
The acs-automated-testing package in the OpenACS CVS is now the master.
The current problem is that we don't have any standard mechanism in place for committing test scripts to individual packages. If we commit them in the standard tcl/xxx-procs.tcl format, then we assume that everyone has the automated testing package installed, which isn't the case. This will result in sourcing errors during bootstrapping etc... What I propose is that we create a "test" directory under the "tcl" directory of the package, and then the bootstrapper will optionally source test scripts if the testing package is installed.
What's the current timeline for the 4.6 and 4.7 releases? It'll depend on the dates as to which release we can get the changes in place for.
