[PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
[EMAIL PROTECTED] (Sascha Schumann) wrote: And we should not close our eyes from the possibility of a 4.3.1 release (e.g. due to a security issue). In that not-so-remote event, having a 4.3 branch with minimal changes is a simple requirement. With 4.3.0 you introduced lots of useful new features and new code (streams, bundled gd, PEAR release) and is - in my eyes - one of the biggest steps since 4.0.0. However - there have also been some new and annoying bugs. So why not release a bugfix 4.3.1 not because of a security hole but just to complete the great work already done on PHP 4.3 - before definitely jumping to PHP 5? Maybe I'm too swissy, but it makes me sad when I see PHP 4 beeing thrown away so fast... and PHP 5 will not be mature with the 5.0.0 release, there will be bugs, missing extensions and so on. Christoph -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
On Wed, 15 Jan 2003, Christoph Grottolo wrote: So why not release a bugfix 4.3.1 not because of a security hole but just to complete the great work already done on PHP 4.3 - before definitely jumping to PHP 5? Who said that we're not going to release a 4.3.1 or 4.3.n? I'm just not favoring new code going into the PHP_4_3 branch, but only bugfixes. I'd like to see new functionality going into HEAD, for PHP 5. Derick -- - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
[EMAIL PROTECTED] (Derick Rethans) wrote: So why not release a bugfix 4.3.1 not because of a security hole but just to complete the great work already done on PHP 4.3 - before definitely jumping to PHP 5? Who said that we're not going to release a 4.3.1 or 4.3.n? I'm just not favoring new code going into the PHP_4_3 branch, but only bugfixes. I'd like to see new functionality going into HEAD, for PHP 5. Maybe I misunderstood when Edin said that there will be no new release for some time due to the move on PHP 5. I completely agree with you, then. Christoph -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
Maybe I misunderstood when Edin said that there will be no new release for some time due to the move on PHP 5. Yes, you misunderstood what I said which was that there is not going to be a release from the HEAD branch for some time to come -- until PHP 5 is released. As a matter of fact I think it would be good idea to go for 4.3.1 in February because number of bugfixes in PHP_4_3 branch is already significant and since no major new features have been added there the QA process shouldn't take that long either. Edin -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
On Wed, 15 Jan 2003, Derick Rethans wrote: On Wed, 15 Jan 2003, Christoph Grottolo wrote: So why not release a bugfix 4.3.1 not because of a security hole but just to complete the great work already done on PHP 4.3 - before definitely jumping to PHP 5? Who said that we're not going to release a 4.3.1 or 4.3.n? I'm just not favoring new code going into the PHP_4_3 branch, but only bugfixes. I'd like to see new functionality going into HEAD, for PHP 5. You might favor that, but I don't pretend that PHP 5.x will become useful immediately for my purposes. I need something to rely on and that is PHP 4 at this time. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
Who said that we're not going to release a 4.3.1 or 4.3.n? I'm just not favoring new code going into the PHP_4_3 branch, but only bugfixes. I'd like to see new functionality going into HEAD, for PHP 5. You might favor that, but I don't pretend that PHP 5.x will become useful immediately for my purposes. I need something to rely on and that is PHP 4 at this time. I completely agree. We can't stall all new development waiting for PHP 5. For example, my little user data filter hook thing would be considered a new feature that I really can't wait for PHP 5 for. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
On Wed, 15 Jan 2003, Edin Kadribasic wrote: Maybe I misunderstood when Edin said that there will be no new release for some time due to the move on PHP 5. Yes, you misunderstood what I said which was that there is not going to be a release from the HEAD branch for some time to come -- until PHP 5 is released. As a matter of fact I think it would be good idea to go for 4.3.1 in February because number of bugfixes in PHP_4_3 branch is already significant and since no major new features have been added there the QA process shouldn't take that long either. There were some, for example Sascha's addition. This alone would qualify a full QA, and not a short and fast one. Our general idea was to NOT add new code to release branches, but at the moment developers are still doing this because *they* need a new function and dont want to wait for 5.0.0. I can understand that they dont want to wait for PHP 5, but what I dont understand is that they think less about the general stability and QA processes for the PHP 4.3.x series. Derick -- - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re[2]: [PHP-DEV] 4.3.1 (was: [PHP-CVS] cvs: php4(PHP_4_3) /main SAPI.h)
DR There were some, for example Sascha's addition. This alone would qualify DR a full QA, and not a short and fast one. Our general idea was to NOT add DR new code to release branches, but at the moment developers are still DR doing this because *they* need a new function and dont want to wait for DR 5.0.0. I can understand that they dont want to wait for PHP 5, but what DR I dont understand is that they think less about the general stability DR and QA processes for the PHP 4.3.x series. As a PHP developper and Hostmaster I really agree with you and I am looking foward a real stable PHP4.3.x with current functionnality and no more ;-) -- Cordialement, Laurentmailto:[EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
