Re: PEAR in PHP releases
| From: | Stig S. Bakken | Date: | Sat, 16 Mar 2002 00:32:21 +0000 |
| Subject: | Re: PEAR in PHP releases | ||
| References: | 1 | Groups: | php.pear.dev php.qa |
| Request: | Send a blank email to pear-dev+get-4989@lists.php.net to get a copy of this message | ||
On Fri, 2002-03-15 at 17:31, Martin Jansen wrote:
> Hi,
>
> some people have complained that the PEAR code that comes with
> the PHP distributions is often outdated. The reason for this
> seems to be the fact, that the people who change code in PEAR
> only merge the changes into HEAD but not into the current release
> testing branch (e.g. PHP_4_1_2).
>
> We have two chances to avoid this in the next release:
>
> 1.: The PEAR developers merge all changes to /php4/pear/* that
> should be in the next release of PHP into the current release
> testing branch after they have commited it to HEAD.
>
> 2.: When releasing a new PHP distribution, the guy, who makes the
> release tarball etc., takes /php4/pear from HEAD and not from
> PHP_4_x_y, so that the most recent version of PEAR is present.
>
> Personally I prefer 1, since we then also have some kind of
> QA for PEAR.
I think 1 is the way to go. I've done it once or twice before, will do
it for 4.2.0 too unless there are wild protests.
- Stig