Karzilla, Destroyer of Bugs (![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
karzilla) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_maintenance2017-04-27 03:03 pm
karzilla) wrote in dw_maintenance2017-04-27 03:03 pm
Code push scheduled for Sunday night
We are planning to do a code push late this weekend, at approximately 8pm PDT / 11pm EDT / 3am UTC on Sunday, Apr 30 (or May 1 for you transatlantic types.).
I don't have a list of changes for you yet, but most will fall into the following categories: things users have complained about to support volunteers, things support volunteers have complained about to developers, thingsdenise has complained about not working the way she expects them to (and as we all know, The Boss is Always Right), and things that were printing warnings over and over in the production server logs, making it hard to spot when less frequent, more urgent errors were being printed. Oh, and also all the unused code I ripped out at the roots, which if you notice that, I did it wrong.
To sum up: we are rolling out a bunch of requested changes, so thank you all for your feedback!
If you're new to Dreamwidth and interested in tracking our development process, our commit logs are published tochangelog and ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
changelog_digest, and every month or so, one of our volunteers will translate those often-cryptic entries into witty, informative code tours! The most recent one was published on April 1, so we're about due for a new one. Hint, hint.
We'll update here again to let you know when the code push is imminent!
I don't have a list of changes for you yet, but most will fall into the following categories: things users have complained about to support volunteers, things support volunteers have complained about to developers, things
denise has complained about not working the way she expects them to (and as we all know, The Boss is Always Right), and things that were printing warnings over and over in the production server logs, making it hard to spot when less frequent, more urgent errors were being printed. Oh, and also all the unused code I ripped out at the roots, which if you notice that, I did it wrong.To sum up: we are rolling out a bunch of requested changes, so thank you all for your feedback!
If you're new to Dreamwidth and interested in tracking our development process, our commit logs are published to
changelog and changelog_digest, and every month or so, one of our volunteers will translate those often-cryptic entries into witty, informative code tours! The most recent one was published on April 1, so we're about due for a new one. Hint, hint.We'll update here again to let you know when the code push is imminent!
no subject
<3