Re: Re: PEAR 1.5.0a1 release checklist
| From: | Pierre | Date: | Sun, 24 Sep 2006 17:59:48 +0000 |
| Subject: | Re: Re: PEAR 1.5.0a1 release checklist | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-3922@lists.php.net to get a copy of this message | ||
Hello,
On 9/24/06, Justin Patrin <papercrane@gmail.com> wrote:
And your TODO list defines when PEAR can be release? I suggest Greg still release it as he has explicitly stated that it is being releases as alpha to allow changing the API of new features.It is my TODO, it is the PEAR Todo. And yes, I like to have a word when PEAR can be released or not. Every point has been discussed before and agreed. And yes, I understand what means alpha, I also like to have the first alpha out with the branches support.
It was a reminder.1) PECL extensions can now be auto-enabled in php.ini on installation, just set php_ini config variable to the path to php.iniAs already explained, this option should accept an array or a file. An alternative solution is to have two options: php.ini and/or php ini direrctoy (just like php). Good point. An alpha release will allow for this to be changed if needed.
Sorry, I meant clarify/document (see other threads), and we have plenty of times, it was also a reminder.2) dialogs for post-install scripts are much more readable and attractive 3) TAP output for run-tests is available 4) PEAR does not contact the internet on installation unless absolutely required 5) deprecated packages display a warning to the user on info/install commands 6) PEAR_Error can be passed to PEAR_Exception as a reason 7) staticPop implemented in PEAR_ErrorStackI would also clear the Exceptions usage prior to 1.5.0. clear? What do you mean?
It is the addition of Zend (talking about the engine here) support. Read the change log and the mails posted in this list (no direct link sorry). We need to update the version (2.0 in 1.4.x) to 2.1.0 or whatever else we need, I'd to go with 2.1.0.in addition, a whole slew of bugs are fixed. In spite of the minor version bump to 1.5.0, this is an incremental upgrade, nothing like the massive changes from 1.3.0 to 1.4.0.As far as I remember, the changes in package.xml have been kept (zend ext). We have to upgrade the package.xml version. zend extensions to the package.xml....?
I also like to add the branches support. It is then possible to include many versions in on package (branches). Each branch can be defined using the known dependencies rules. It is now critical to have it. What is "branches support" exactly and why is it critical to have it?Do you know what is a CVS branche or a SVN tag? I suppose yes, it is the same principle. It will allow to release one package for all targets. For example, in PECL, all extensions have branches for php4, 5 and 6 (both for pecl and php if the ext is bundled in php). Problem, it is not always possible to release a package compatible with all desired targets. A partial solution is to use an insane amount of #ifdef in your code or to name files diffentely (valid for php scripts). However some files cannot be duplicated and automatically used by the installer. A good example is the config.m4 file. it is a critical part of the pecl build sytem. Its content must match a given PHP version (take a look at the libxml related m4 macros for example). Having branches support will all any developer to provide full support for any PHP versions within one single release. It can also be used to provide php5 and 6 version of a PHP "script" only package, I think it will be more than usefull in this case, but it is not the reason why it is critical, pecl is the reason. --Pierre