denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_maintenance2012-03-24 01:06 am

Code pushed!

The code push is now complete! Please report any problems here for the next 24 hours or so (and to Support after that).

Code tours describing changesets included in this push are:

* 22 Feb - 13 Mar
* 14 Mar - 23 Mar

In particular, we're asking people to turn on the "New JS on Journals" option on the Beta Features page. We've finished converting all the JavaScript inside your journal to JQuery, the more modern JavaScript library we're moving towards. The version available for beta testing now is the release candidate. With the next code push, we will be opting everyone into that beta (with the ability to still opt out of the beta version if you discover a showstopper bug that prevents you from using your journal); with the code push after that, the code will be taken out of beta and you will no longer be able to turn off the new JavaScript behavior at all.

So, turn on the beta now, and report any bugs with JavaScript in your journal to the [site community profile] dw_beta "Last Call" post if you're sure it's related to the new JavaScript, or here if you aren't sure whether or not it's an issue with the new JS!
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2012-03-24 08:52 pm (UTC)(link)
I'm just another user here, but - for the most part, everything will look pretty much the same. The Javascript update makes the icon browser look slightly different, but have basically the same functionality, and everything else is the same. It's pretty much all hidden work on the scripts that run display, to make them more modern, and easier for new developers to work on. That's why everyone is being opted in, with eventually no option to opt out - the clunky old code will be gone.
esteven: (Default)

[personal profile] esteven 2012-03-25 07:26 am (UTC)(link)
Thank you for making it clearer to me in more one-syllable words. :D But if everything is pretty much the same, then why do I read of firefox freezing, screen fatigue, difficulties in cross-post settings and emptying caches, all of which would not happen/be necessary if everything stayed much as it is?

Sorry to be such a looby, and thanks again for your patience.
esteven: (Default)

[personal profile] esteven 2012-03-25 07:49 am (UTC)(link)
I understand perfectly what you are trying to say, I just don't understand the words you use (that is why I thanked [personal profile] momijizukamori for her translation for ejits).

Still, I appreciate that you are doing a good job for your users.
esteven: (Default)

[personal profile] esteven 2012-03-25 05:58 pm (UTC)(link)
Thank you so much for giving me your time and patience. You were really trying hard and I commend you for that.
*raises glass to you*

It is not your fault that I cannot build Lego cars either ;D and am deeply mistrustful of changes I'll have to see what comes out of your code push and how it will affect my comfort at DW. I would really hate to leave.

Thank you once more. :D
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2012-03-25 07:42 am (UTC)(link)
Well, the screen fatigue is from the icon browswer redesign. And crosspost settings are from the other beta feature, which is the new update page they've been working on for months. I don't really know about the Firefox crashes - cache-clearing is an unfortunate side effect of moving from old code to new. If your browser still has the old code saved in it's cache, it has to be cleared for the new to work properly. Usually it does it automatically, but sometimes it doesn't update properly, and clearing it should be a one-time only deal if necessary.

So yes, these wouldn't be problems if stuff stayed the same - but we'd have other problems in the form of outdated code or code that isn't easy to work with (and the old icon-browser has problems with it's design, which is why it's being updated).