Post diffs of style changes right before a code push

[zvi]

Title:
Post diffs of style changes right before a code push

Area:
styles, communications, codepushes

Summary:
The styles team is working to improve the CSS for official styles all the time. Sometimes people like the unimproved style or their customizations are based on the imperfections. We should give people more info so they can fix their customizations after code pushes.

Description:
Specifically, when a code push is going live, there should be an entry on DW-styles that explains what changes are being made to any layouts or themes. Calling it a diff is a bit of a misnomer, because I think it should include more info than that, i.e.

1) The old code
2) The new code
3) A plain English explanation of what both sets of code do, and the problem being solved by changing the code.
4) The custom CSS/changed wizard settings required to get the old behavior back on the default layout and theme.

Drawbacks: This will require more work on the part of the styles team and more warning from The Bosses that a code push is coming than is now the custom. People will still be unhappy that we're making them make a change instead of offering two versions of the code and putting them on the unchanged version.

Poll #1537 Post diffs of style changes right before a code push

Open to: Registered Users, detailed results viewable to: All, participants: 21

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
16 (76.2%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (23.8%)

(Other: please comment)
0 (0.0%)

Comments

[matgb]

I agree with this--friend of mine has a permanent LJ account but backs up to DW irregularly and comments here regularly. She hadn't looked at her journal here since July, and it was really messed up due to some code changes.

She's my go-to when I get confused on CSS stuff, she's good, but unnanounced changes mess up a lot of styles.

[afuna]

I like compiling a list of things that changed + additional information. For best results (sanity of everyone involved), I think it would be good if we could have multiple people coordinating to compile a list in a central location as an ongoing effort, and then publish it when code push comes.