jQuerify journals status
Mar. 21st, 2012 03:07 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
foxfirefeyBug 3532, the jQuerify journals bug, is moving towards completion. On the next code push, there will be a post to ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_beta for any remaining issues people are having. They'll be fixed and/or filed, depending on urgency, so that we can then turn on the jQuery for everyone, while still giving people a chance to turn the jQuery off. I imagine once all the issues are taken care of, the old journal Javascript will be deprecated and then removed.
For development, this means patches for old journal Javascript will no longer be accepted. If you see a bug open for old journal JS, it can be closed. (Don't do that if it's something that involves doing JS for the new JQuery version, though.)
( Extra info on: Why JQuery-izing? )
dw_beta for any remaining issues people are having. They'll be fixed and/or filed, depending on urgency, so that we can then turn on the jQuery for everyone, while still giving people a chance to turn the jQuery off. I imagine once all the issues are taken care of, the old journal Javascript will be deprecated and then removed.For development, this means patches for old journal Javascript will no longer be accepted. If you see a bug open for old journal JS, it can be closed. (Don't do that if it's something that involves doing JS for the new JQuery version, though.)
( Extra info on: Why JQuery-izing? )