Code push scheduled for Sunday night

Apr. 27th, 2017 03:03 pm
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla posting in [site community profile] dw_maintenance
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, things [staff profile] 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 [site community profile] changelog and [community profile] 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!

The importer has (mostly) caught up!

Apr. 19th, 2017 11:02 pm
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_maintenance
Our content importer has mostly caught up with its backlog; almost everything that's still listed as being "in the queue" are jobs that were tried, failed once or more with a temporary failure, and are waiting to try again. (The importer tries a few times, at successively longer intervals, when it gets a failure it thinks might be temporary/might correct itself later on.) This means that new imports scheduled now should complete in hours (or even minutes), not the "several days" it's been taking.

If you tried to schedule a second import while the first one was still running, at any time in the past 10 days or so, you may have confused the poor thing. If you think your import should be finished by now and it isn't, and you're seeing "Aborted" on the Importer Status part of the Importer page, feel free to open a support request in the Importer category and we'll look into it for you. (It may take a little bit before you get a response; those of us who have the access to look into importer problems have been really busy for the past two weeks or so, and I at least need a few days to catch my breath a bit before diving back into the fray! But we'll do what we can.)

I hope all y'all are continuing to settle in well to your new home!

Profile

bunrab: (Default)
bunrab

April 2017

S M T W T F S
      1
2345678
91011 12131415
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Apr. 30th, 2017 12:54 pm
Powered by Dreamwidth Studios