[theme-reviewers] how to handle 3.3 deprecated notice?

[Otto]

Please don't reply to digest emails.

And no, I wouldn't ignore such things. 3.3 is in beta 2 and well on
track for release very soon. It would be a good idea to future proof
things.

That message, BTW, comes to you courtesy of the "_doing_it_wrong"
function in WordPress. If you trigger it, then you're doing something
wrong.

-Otto



On Mon, Oct 24, 2011 at 10:13 AM, Paul de Wouters
<pauldewouters at zoho.com> wrote:
> Hi
> Should I ignore deprecated notices relative to version 3.3?
>
> Scripts and styles should not be registered or enqueued until
> thewp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please
> seeDebugging in WordPress for more information.
> This message was added in version 3.3.
> Should testing be done using the current stable version?
> thanks