Re: A suggestion regarding stabel vs. experimental on the extension level

At 19:00 16/11/2000, Rasmus Lerdorf wrote:

The main problem with this is that you can't really move files around in CVS nicely without some ugly hacks or without losing the revision history for those files. I would rather see some sort of indicator put into an ext/ directory that simply prevents it from being included in a release. eg. ext/foo/EXPERIMENTAL We can simply check for that file and not include the extension if it is there. That eliminates the need for shuffling files around in the CVS repository.

Actually it's quite possible, just not through CVS. If you move the ,v files, it would just work, and all of the revision history will be retained. I don't think that the experimental code should be excluded from releases (which will reduce the number of bug reports, and 'turn around time' from unstable to stable status for modules). Instead, if we could somehow clearly state that the extension is experimental, like force the switch to be --with-experimental-SOMETHING, then it should be ok. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/