Forum OpenACS Q&A: Re: invalid command name "throttle"

Posted by Janine Ohmer on
The problem with this way of doing things is that it IMHO makes things unnecessarily complicated.

Someone like Ben, who knows what packages he wants to install, can't get at them unless he checks them out from CVS, on a tag he's not likely to know. So he's stuck.

Someone who wants to try out the toolkit is going to walk away thinking the core is all there is, since there are no clues to tell him that anything else is availble. If he doesn't get it in the tarball, and doesn't see it in the Repository, it's not going to exist for him.

It's a nice idea to say that we're only going to tag packages that are tested, but since no-one is doing any testing that effectively hides those packages from anyone who is not a developer.

I think it would be better to tag everything when tagging a release, and then make those packges available in the Repository with maturity levels clearly visible. Maybe it should be called 'level of testing' instead, so that a level of zero would clearly indicate 'not tested at all'.

Just MHO...

Posted by Malte Sussdorff on
Janine, I'd agree and say that we should control the packages both by tagging them once someone got it running in a certain environment and using the maturity level to prevent someone like Ben of running into problems. Maybe an warning sign stating "You are about to install untested code. This will most likely result in data loss and a destruction of your current website. You are expected to run into a lot of bugs and the level of frustration you will experience can be tremendous. Please rethink your choice of installing the following packages (list of packages with maturity level 0). Otherwise proceed at your own risk and please report any problems you encounter to"; will do.