Re: Re: PEAR 1.5.0a1 release checklist
| From: | Justin Patrin | Date: | Sun, 24 Sep 2006 17:12:58 +0000 |
| Subject: | Re: Re: PEAR 1.5.0a1 release checklist | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-3920@lists.php.net to get a copy of this message | ||
On 9/24/06, Pierre <pierre.php@gmail.com> wrote:
Hello, On Sun, 24 Sep 2006 01:04:37 -0500 greg@chiaraquartet.net (Greg Beaver) wrote: Hi everyone, I plan to release PEAR version 1.5.0a1 on September 30. New features include: It is too early sorry. Mid-october sounds more appropriate. Besides the current PHP releases, I have other things in the TODO list. See below.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.
1) PECL extensions can now be auto-enabled in php.ini on installation, just set php_ini config variable to the path to php.ini As 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.
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_ErrorStack I would also clear the Exceptions usage prior to 1.5.0.clear? What do you mean?
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? -- Justin Patrin