Re: Re: is_a() - again - a better fix
| From: | Jan Schneider | Date: | Tue, 25 Oct 2011 08:59:11 +0000 |
| Subject: | Re: Re: is_a() - again - a better fix | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-55952@lists.php.net to get a copy of this message | ||
Zitat von Ferenc Kovacs <tyra3l@gmail.com>:
On Thu, Oct 6, 2011 at 2:49 PM, Jan Schneider <jan@horde.org> wrote:FWIW it seems to be more stable now since upgrading to a newer Jenkins version. Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/Zitat von Pierre Joye <pierre.php@gmail.com>:http://www.downforeveryoneorjustme.com/ci.horde.org "It's not just you! http://ci.horde.org looks down from here."On Fri, Sep 23, 2011 at 12:23 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:http://ci.horde.org/ If using the released versions, that would add another 5000 tests.On 09/23/2011 12:17 PM, Pierre Joye wrote:Right, also reported back then with the same success ;) Anyway, that's past, the BC break has been fixed and we are working to get these apps&frameworks tests result as part of our release process (symfony and doctrine are on the road, must see with zf if we can share resources as they do it anyway internally).We do 2) already (while we are working on increasing the amount of apps and frameworks being tested), as I was asking to revert this patch between 5.3.7 and 5.3.8 back then pointing to our tests results and numerous reports. The problem was not in the QA but in the decision process. QA should have a kind of veto power in this case to avoid arguing and still have BC breaks landing in stable releases.Well, 5.3.7 - 5.3.8 wasn't really the problem. That release was rushed to fix my crypt screwup. This should have been caught in the 5.3.6 - 5.3.7 testing which lasted much longer than the short window to 5.3.8.