Newsgroups: php.internals,php.pdo
Path: news.php.net
Xref: news.php.net php.internals:49006 php.pdo:464
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Stanley Sufficool <ssufficool@gmail.com>
Cc: PHP internals list <internals@lists.php.net>, pdo <pdo@lists.php.net>
In-Reply-To: <AANLkTikudsMYBZVhmkAjrZX5Zw4oSxpdwDLAA-oGXemq@mail.gmail.com>
References: <AANLkTikudsMYBZVhmkAjrZX5Zw4oSxpdwDLAA-oGXemq@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 06 Jul 2010 10:08:58 +0200
Message-ID: <1278403738.5578.267.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PDO DBLIB Release Candidate?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2010-07-02 at 07:11 -0700, Stanley Sufficool wrote:
> Can I get an affirmation if the pdo dblib code will be accepted in 5.2
> and 5.3 branches?

In general bug fixes should go to all active branches. Right now these
are 5.2, 5.3 and trunk. Right now 5.2 and 5.3 are in RC so only
"critical" stuff should go in. Afaik this will be the last "regular" 5.2
release only followed only by security related releases from that
branch, but that's up to Ilia. Now the question is about the definition
for "critical" stuff, in doubt that has to be decided by the extension
maintainer and the RMs case by case. (how critical is the issue for
users? how complex(=risky) is the patch? ...) According to the
EXTENSIONS file pdo_dblib isn't maintained right now so thank you for
volunteering to take over that role.

johannes