Or perhaps tailor the deprecation warning a little? (Nevermind, I just
wrote it out and it gets ugly)
Or perhaps just stick with status quo and add a note to the manual. :DThat might be best.
Christoph M. Becker
Adding a note to the manual sounds like a fair compromise to me. I kind of assumed
we couldn't raise the version on an already released branch, but I still wanted to
bring it up since the behavior seemed broken. I contacted the hosting provider about
their ancient ICU version, but they weren't very amenable to upgrading to a more recent
version.
Or perhaps tailor the deprecation warning a little? (Nevermind, I just
wrote it out and it gets ugly)
Or perhaps just stick with status quo and add a note to the manual. :DThat might be best.
Adding a note to the manual sounds like a fair compromise to me.
Fine. Done with http://svn.php.net/viewvc?view=revision&revision=347889.
I kind of assumed
we couldn't raise the version on an already released branch, but I still wanted to
bring it up since the behavior seemed broken. I contacted the hosting provider about
their ancient ICU version, but they weren't very amenable to upgrading to a more recent
version.
https://www.cvedetails.com/vulnerability-list/vendor_id-17477/Icu-project.html
--
Christoph M. Becker