On Nov 29 2010 3:48 PM, Andrew Nacin wrote:
On Mon, Nov 29, 2010 at 3:46 PM, Jon Cave<[email protected]> wrote:
On Mon, Nov 29, 2010 at 8:41 PM, Dougal Campbell<[email protected]>
wrote:
I don't know if we want to change anything in core's behavior regarding
this
before release, but if not, we should probably get the word out for
plugin
authors to double-check their code ASAP.
http://core.trac.wordpress.org/ticket/14729
Already posted by Nacin to this list. In the beta post on
wordpress.org [1] and was also mentioned on wpdevel.wordpress.com, but
don't have that link to hand.
[1] http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/
For reference, here's the previous post to the list:
http://lists.automattic.com/pipermail/wp-testers/2010-November/013746.html
<http://lists.automattic.com/pipermail/wp-testers/2010-November/013746.html>Dougal,
in a nutshell, your suspicions were entirely correct. We're going to leave
the fatal errors in here for as long as possible, probably removing them
prior to the final RC.
Help us get the word out more than we already have :-)
Okay, sorry I didn't spot that before posting. I did do a quick scan of
message subjects for the last couple of days, but still managed to miss
it. Between starting a new job just a couple of weeks ago and the
Thanksgiving holiday, my email-fu has been low lately. :)
Glad to know that it's already been spotted, and that there's a plan in
place. I think leaving it as a fatal until the last minute, then putting
a guard in sounds like a good way to handle it.
--
Dougal Campbell <[email protected]>
http://dougal.gunters.org/
http://twitter.com/dougal
http://twitual.com/
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
