On Fri, 8 Aug 2008, Rui Hirokawa wrote:
> "Chris Stockton" <[EMAIL PROTECTED]> wrote:
>
> > fixed bug #27421 (by david at dfoerster dot de) mbstring.func_overload
> > set in .htaccess becomes global
>
> There are a typo in NEWS of PHP 4.4.9.
> #37421 should be #27421.
Fixed
Derick
--
HEAD be
There are a typo in NEWS of PHP 4.4.9.
#37421 should be #27421.
> fixed bug #27421 (by david at dfoerster dot de) mbstring.func_overload
> set in .htaccess becomes global
Rui
On Thu, 7 Aug 2008 14:09:47 -0700
"Chris Stockton" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Is the link in the changelo
Hello,
Is the link in the changelog pointing to the wrong bug? Seems mb related but
speaks of mysqli. Just something small I noticed.
-Chris
On Thu, Aug 7, 2008 at 1:47 PM, Derick Rethans <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The PHP development team would like to announce the immediate
> ava
Don't you guys have bigger fish to fry?
--
-
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
On 7 Jul 2008, at 14:00, Rasmus Lerdorf wrote:
Derick Rethans wrote:
On Mon, 7 Jul 2008, Marcus Boerger wrote:
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will
pick up
that patch anyway. But at least we didn't
Derick Rethans wrote:
On Mon, 7 Jul 2008, Marcus Boerger wrote:
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will pick up
that patch anyway. But at least we didn't do a release as we promised, we
wouldn't.
Uh, n
Derick Rethans wrote:
On Mon, 7 Jul 2008, Marcus Boerger wrote:
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will pick up
that patch anyway. But at least we didn't do a release as we promised, we
wouldn't.
Uh, n
On Mon, 7 Jul 2008, Marcus Boerger wrote:
> this can be continued forever. Say we release 4.4.9, then sooner or
> later people will find another security whole, so we do another release.
> And another release and in the year 2134 our childrens children will
> release 4.4.4363
Uh, no. The last d
On Mon, 7 Jul 2008, Marcus Boerger wrote:
> how about this. We edit php_config.h to be version 4.4.8pl1. Then
> provide a patch for download. All reasonable distributions will pick up
> that patch anyway. But at least we didn't do a release as we promised, we
> wouldn't.
Uh, no. We didn't promi
Hello Derick,
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will pick up
that patch anyway. But at least we didn't do a release as we promised, we
wouldn't.
marcus
Monday, July 7, 2008, 9:09:51 AM, you wrote:
> Hel
Hello Stefan,
this can be continued forever. Say we release 4.4.9, then sooner or
later people will find another security whole, so we do another release.
And another release and in the year 2134 our childrens children will
release 4.4.4363
marcus :-)
Monday, July 7, 2008, 3:28:54 PM, you wrot
> Sent: Monday, July 07, 2008 9:07 AM
> To: Andi Gutmans
> Cc: Derick Rethans; Marcus Boerger; PHP Internals; Janusz Lewandowski
> Subject: Re: [PHP-DEV] PHP 4.4.9
>
> On Mon, Jul 7, 2008 at 10:29 AM, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> >
> > I'm with De
On Mon, Jul 7, 2008 at 10:29 AM, Andi Gutmans <[EMAIL PROTECTED]> wrote:
>
> I'm with Derick here. We should push out new releases when there are security
> issues
As am I. The EOL announcement itself justifies the release:
"We will continue to make critical security fixes available on
Hello,
On Mon, Jul 7, 2008 at 9:29 AM, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> > On Mon, 7 Jul 2008, Marcus Boerger wrote:
> >
> > > Janusz is damn right here. Make the patches available but do not
> > > make it easy for people to stick to 4 please. Instead, stick to th
> > > eplan.
> >
> > W
> -Original Message-
> From: Derick Rethans [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 07, 2008 7:22 AM
> To: Marcus Boerger
> Cc: PHP Internals; Janusz Lewandowski
> Subject: Re: [PHP-DEV] PHP 4.4.9
>
> On Mon, 7 Jul 2008, Marcus Boerger wrote:
>
>
On Mon, 7 Jul 2008, Marcus Boerger wrote:
> Janusz is damn right here. Make the patches available but do not
> make it easy for people to stick to 4 please. Instead, stick to th
> eplan.
We do, there are security fixes - we make a release.
regards,
Derick
--
Derick Rethans
http://derickret
Hi Stefan,
Considering the fact that PHP 4.4.8 is known to have several public
security problems that where only fixed in PHP 5, releasing PHP 4.4.9
as last final version is the right thing todo.
Fixing any major security hole in 4.4 at this point would put an abrupt end
to this argument ;)
On Mon, Jul 7, 2008 at 10:39 AM, Janusz Lewandowski <[EMAIL PROTECTED]> wrote:
> 2008/7/7 Guilherme Blanco <[EMAIL PROTECTED]>:
>> The end of life cycle of PHP4 is 08-08-08, so people expect one last
>> release in this day as the last release.
>> Some of you are telling that release something now c
2008/7/7 Guilherme Blanco <[EMAIL PROTECTED]>:
> The end of life cycle of PHP4 is 08-08-08, so people expect one last
> release in this day as the last release.
> Some of you are telling that release something now contradicts your
> master plan, but you missed something.
>
> If you don't release so
Hi,
I do not have karma, but I still think you guys missed one point in
the entire thing.
The end of life cycle of PHP4 is 08-08-08, so people expect one last
release in this day as the last release.
Some of you are telling that release something now contradicts your
master plan, but you missed s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Janusz Lewandowski schrieb:
> PHP 4 end of life announcement:
>> After 2007-12-31 there will be no more releases of PHP 4.4.
>> We will continue to make critical security fixes available
>> on a case-by-case basis until 2008-08-08.
Considering the fac
On Mon, Jul 7, 2008 at 3:02 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Derick,
>
> Janusz is damn right here. Make the patches available but do not make it
> easy for people to stick to 4 please. Instead, stick to th eplan.
I tend to agree here, a new release may contradict the purpose
Hello Derick,
Janusz is damn right here. Make the patches available but do not make it
easy for people to stick to 4 please. Instead, stick to th eplan.
marcus
Monday, July 7, 2008, 1:15:19 PM, you wrote:
> PHP 4 end of life announcement:
>> After 2007-12-31 there will be no more releases of
PHP 4 end of life announcement:
> After 2007-12-31 there will be no more releases of PHP 4.4.
> We will continue to make critical security fixes available
> on a case-by-case basis until 2008-08-08.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/
On Mon, 7 Jul 2008, Jani Taskinen wrote:
> Hannes Magnusson wrote:
> > On Mon, Jul 7, 2008 at 09:09, Derick Rethans <[EMAIL PROTECTED]> wrote:
> > > Hello!
> > >
> > > As it's about a month until the end of PHP 4, it's time to make the last
> > > release. There have been a few important fixes, wh
Hannes Magnusson wrote:
On Mon, Jul 7, 2008 at 09:09, Derick Rethans <[EMAIL PROTECTED]> wrote:
Hello!
As it's about a month until the end of PHP 4, it's time to make the last
release. There have been a few important fixes, which need to be part of
a release.
Out of curiosity, which ones and
On Mon, Jul 7, 2008 at 09:09, Derick Rethans <[EMAIL PROTECTED]> wrote:
> Hello!
>
> As it's about a month until the end of PHP 4, it's time to make the last
> release. There have been a few important fixes, which need to be part of
> a release.
Out of curiosity, which ones and why aren't they in
27 matches
Mail list logo
