Re: [PHP-DEV] 5.4 non-security issues - last call
[email protected] ("Matt Wilmas")
| Newsgroups | php.internals |
|---|---|
| Message-ID | <AB1D015FF9C14A2DA467D15B8A67027C@pc1> |
Hi Stas! ----- Original Message ----- From: "Matt Wilmas" Sent: Friday, August 29 > Hi Stas, all! > > ----- Original Message ----- > From: "Stas Malyshev" > Sent: Thursday, August 28, 2014 > >> Hi! >> >> 5.6.0 has been released, and first thing I'd like to congratulate all >> who participated in it with this great milestone. >> >> Second thing, that means 5.4.33 would be the last release including >> non-security fixes. With RC1 planned next Tuesday, this means if you've >> got any non-security issues that should be in 5.4 they should be in by >> Tuesday or chance of getting them in would be very low. >> >> [...] >> >> If there are any more issues that need to be in 5.4.33 RC1 please tell >> me ASAP. > > I'd like to finally present a fix/improvement for bugs #64370, #64633, > #65626 (I think), etc... Regarding microtime() resolution on Windows, and > have it included in 5.4 also! > > I had a couple Twitter messages with Pierre and Anatol in October about > how to restore old behavior (and fix issues), and didn't implement my idea > right then... :-/ I almost got around to it this spring after learning > *something* (don't remember) that allows a simpler solution, at least. > > Anyway, hopefully it'll be OK for 5.4 since it's Windows-only, similar to > what we had previously (w/o issues!), and microtime() has been kinda > useless on XP-7 since 5.4.14. The Windows microtime() patch is ready and I just sent a message about it. Assuming it's acceptable in general, can we PLEASE get this fix into 5.4? :-) I didn't realize we were getting releases so often, especially with 5.4 now... After .32 for the *last* non-security release. *shrug* Thanks, Matt