Re: Re: IT[X] status update and a reminder
| From: | Joye Pierre-Alain | Date: | Sun, 23 Feb 2003 20:58:45 +0000 |
| Subject: | Re: Re: IT[X] status update and a reminder | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13680@lists.php.net to get a copy of this message | ||
> Everybody relax !
The only one to be relax is Alexey. Alexey is maybe new to OpenSource
projects, and how they work, change, involve. I doubt, but I can be wrong.
> If i understood your new class behaves the same way s the current one by
default. The user can then change the behaviour, right ?
No, it does not.
> Now, it is just one file, i do not see the difficulty in having a patch, a
cvs diff -u will do right ? (note, that is just a question, it's not angry
toned or anything like that ;)
Indeed, but, imho, the technical questions has been solved and widely agreed
in the last flamewar. The point araised here is the way Alexey has voluntary
choosed, and, most important, do we allow this kind of things in PEAR. I do
not.
So, as en endpoint, near all needed stuffs will be added (see my last post
in the last flamewar), indeed the cache will not be included, the default
way is the actual way, and the new things will be activated using flags.
That will not break any working script around, BC is safe, a clear notice
about that will be added too in the release notes. Then, in the next major
version, when people really got times to be well informed, has really tested
the new things and validate them with their respective applications, we can
plan to change the default behiavors.
pierre