Re: PEAR 1.5.0a1 release checklist
| From: | Greg Beaver | Date: | Mon, 25 Sep 2006 05:23:54 +0000 |
| Subject: | Re: PEAR 1.5.0a1 release checklist | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-3931@lists.php.net to get a copy of this message | ||
Pierre 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.
>
>
>>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).
this can always be updated post-alpha 1. When you say an array, I
assume you mean multiple paths to php.ini. obviously one cannot pass an
array on the command-line. Perhaps better is to allow passing in with
PATH_SEPARATOR
pear config-set php_ini /path/num1/php.ini:/path/num2/php.ini
or on windows:
pear config-set php_ini /path/num1/php.ini;/path/num2/php.ini
this is trivial to implement and would simply be an extension of the
existing code, without breaking BC. Passing a directory does not sound
good, it's possible to have other .ini files in there that are not
php.ini files.
> I would also clear the Exceptions usage prior to 1.5.0.
PEAR doesn't use exceptions, so no real need to do this. PEAR_Exception
is not related to the political discussions.
> As far as I remember, the changes in package.xml have been kept (zend
> ext). We have to upgrade the package.xml version.
This is fully implemented now.
> 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.
As I said in a previous email, this is already possible, so as it
stands, there are no feature implementation issues preventing release of
a first alpha on the 30th, as previously announced.
Now we must simply make sure QA is up to snuff.
Thanks,
Greg