Sorry, I don't see how offering broken code is a coode option.
There are many people with CVS commit who have the ability to test and tag packages. If you are using a package and it works, tag it. The instructions on how to release a package are http://www.openacs.org/doc/openacs-5-2/releasing-package.html
It's pretty easy. I will try to release stuff I know works, specifically packages on openacs.org. I am pretty sure there are broken packages and changing one broken procedure for another isn't going to make Ben's life any easier.
We need to change the process and make it work, the old process of trying to package up and tag a couple hundred packages was not any better, just different.
I will add updating the maturity flag in the release docs, it makes sense to check/update that when you change the version number.
I think we are getting better, we need this kind of feedback so we can improve OpenACS. Any help in tagging packages on the oacs-5-2 branch as opeancs-5-2-compat would be appreciated. I haven't had time to go through and increase the version numbers and mark those packages.
