Thu, Mar 21
T217469 had a patch deployed... Is the issue on this task fixed, also, maybe?
Columned my update.
Tue, Mar 5
Thu, Feb 28
Tue, Feb 26
Just to note, additional developer setup required for the fundraising vagrant role (such as perhaps specific XDebug stuff) should also be documented.
Here are the unfinished drafts from a while ago.
Feb 19 2019
Feb 14 2019
Feb 12 2019
Feb 11 2019
Feb 8 2019
Following IRL discussion with @thcipriani, it seems there's a pretty easy solution! If the script that automatically generates release branches for extensions can be made to create branches based on wmf_deploy, rather than master, that would allow us to keep fine-grained control over how and when things are deployed, and at the same time let deployments use existing standard procedures. Any thoughts? Thanks in advance!!!!
Feb 7 2019
T215086 just merged into CentralNotice master. It should go out with the train next week.
Feb 6 2019
Feb 5 2019
Feb 2 2019
Jan 25 2019
I just re-ran the query, and the results are the same, as expected.
Jan 24 2019
I've set up a test banner with a JS error on the beta cluster.
Just FYI, here's the task about the data discrepancy: T214600.
Here is the data from Hive for actual calls to Special:BannerLoader to load and inject the banner into the page. The Hive query used follows.
Jan 23 2019
@Krinkle , thanks much for the great explanation!
Jan 22 2019
Jan 21 2019
I've updated the mobile banner. I don't think it will cause errors now. I also added an alterImpressionData function to get correct data about whether or not the banner was displayed.
Jan 18 2019
Jan 17 2019
Pulled this onto deploy1001 in the staging dir for wmf.12. git status no longer shows new commits in extensions/CentralNotice. :)