Re: Re: svn: /pear/packages/Log/trunk/ package.php package.xml
| From: | Helgi Þormar Þorbjörnsson | Date: | Tue, 29 Dec 2009 19:19:31 +0000 |
| Subject: | Re: Re: svn: /pear/packages/Log/trunk/ package.php package.xml | ||
| References: | 1 2 3 4 | Groups: | php.pear.cvs php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53177@lists.php.net to get a copy of this message | ||
On 28 Dec 2009, at 20:00, Brett Bieber wrote:
> 2009/12/28 Alexey Borzov <borz_off@cs.msu.su>:
>>
>> Helgi Þormar Þorbjörnsson wrote:
>>>
>>> You can not presently drop PHP 4 support in a minor release like that
>>> unless I'm missing some changed rules?
>>> Please correct me if I'm wrong.
>>
>> We only have guidelines for BC breaks:
>> http://pear.php.net/group/docs/20031114-bbr.php
>> http://pear.php.net/group/docs/20040226-vn.php
>>
>> I don't see a BC break for PHP4 users here since they'll not be able to
>> upgrade to a new version in the first place.
>>
>> So the only question is whether there is a BC break for PHP5 users in these
>> changes.
>>
>> We also have a rule that new packages / new major versions should be
>> E_STRICT but this does not apply here.
>
> I see nothing wrong with the new release requiring PHP5 as long as the
> API isn't changing.
>
> Furthermore, if you're interested in API changes that break BC
> (without changing the package name), you should call your local PEAR
> group representative and get them to pass this -
> http://wiki.php.net/pear/rfc/pear2_versioning_standard_revision
> and
> backport it to PEAR(1).
Alright lets then keep this as is, I would have thought excluding users that could use it before was
not allowed but alas.
The question becomes, is the PEAR installer smart enough to tell PHP 4 people to keep upgrading
within 1.11.x instead of trying to do 1.12+ and constantly failing.
Currently I'm not sure.
I suggest that Jon you don't propose a Log2 or such anytime soon, at least wait for a proposal
I will be pushing through fairly soon, which should be to your satisfaction ;-)
Regards
Helgi