Re: How critical does a bug need to be to warrant a new PHP release (like 5.1.5)?

From: Date: Fri, 26 May 2006 03:05:39 +0000
Subject: Re: How critical does a bug need to be to warrant a new PHP release (like 5.1.5)?
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-23682@lists.php.net to get a copy of this message
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Would you care to elaborate? Maybe a sample script that exhibits this behaviour? Jasper steve wrote: > What if it requires a PHP script flaw also (like calling a method from > an object that doesn't exist)? I can shut down many a site that have > 5.1.4 if I can find some input to expose a script flaw like that, if > their setup is similar to mine (which I think is common). Damn search > engine came across such a bug of mine on a test site and shut it down. > Killed a couple others it wasn't searching because of it also. > Accidental DOS! Oh the joy... > > :( > > Oh well, 5.1.2 works fine for now. > > On 5/25/06, Pierre <pierre.php@gmail.com> wrote: >> On 5/26/06, steve <iamstever@gmail.com> wrote: >> > How critical does a bug need to be to warrant a new PHP release (like >> > 5.1.5)? Are there specific criteria already laid out? >> >> Security issues or critical bugs (for example segfaults or huge leaks >> not managed by the memory manager). Ilia will certainly complete this >> list :-) >> >> --Pierre >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEdnCDFfAeHhDzT4gRA4iqAKCQFanzjvSiF2+k+ChCc9Dj6m9N5ACgkLDS ICdJtzKh99zrdnR/PYwgK+A= =ocva -----END PGP SIGNATURE-----

« previous php.internals (#23682) next »