Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4088
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3F41E33C.4080805@reach.co.za>
Date: Tue, 19 Aug 2003 10:43:40 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: ilia@prohost.org, internals <internals@lists.php.net>
References: <200308181010.43254.ilia@prohost.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 4.3.3RC4 Released
From: cornec@reach.co.za ("Corne' cornelius")

Hi,

I have a patch for the Informix extensions that fixes a bug which is 
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416, 
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in 
PHP-4.3.3 final ?

or do i need to commit it to  PHP_4 now, and to PHP_4_3 after 4.3.3 
final is released ?

Thanks,
Corne'


!Exclude Disclaimer!

Ilia Alshanetsky wrote:

>RC3 did not prove as stable as I hoped it would be, so here we are 20+ bug 
>fixes later with RC4. It is my sincere hope that RC4 will be the last RC 
>before we can proceed with the final. Please test this release as much as 
>possible, ideally you won't find any new bugs.
>
>Once again I would like to ask that all developers refrain from making commits 
>to the 4_3 tree until 4.3.3 final is released, unless a patch addresses a 
>critical issue. Critical issues are defined as the following:
>1) Security Fixes
>2) Fixes for bugs introduced in 4.3.3X releases
>3) Fixes for bugs that break backwards compatibility with older versions.
>
>Ilia
>
>
>  
>