nyuuzyou/wikis huggingface dataset:
Deployments/Archive/2019/02

=== Week of February 4th ===
* Week of:
** nothing yet...
; By day
=== Week of February 11th ===
* Week of:
** Deploy schema changes: 
; By day
=== Week of February 18th ===
* Week of:
** Monday Feb 18: US Holiday, no deploys
** Deploy schema changes: 
; By day
=== Week of February 25th ===
* Week of:
** Deploy multiple schema changes: 
** Clean up orphaned echo_event rows: (starting on Wednesday)
; By day
Deployments/Archive/2019/03

=== Week of March 4th ===
* Week of:
** nothing yet...
; By day
=== Week of March 11th ===
* Week of:
** Schema change to unify the logging table: 
; By day
=== Week of March 18th ===
* Week of:
** Schema change to unify the logging table: 
; By day
=== Week of March 25th ===
* Week of:
** Schema change on logging table: T71127 T51199
; By day
Deployments/Archive/2019/04

=== Week of April 1st ===
* Week of:
** Anomie will be running a maintenance script on the log_search table for T215525.
; By day
=== Week of April 8th ===
* Week of:
** 
; By day
=== Week of April 15th ===
* Week of:
** 
; By day
=== Week of April 22nd ===
* Week of:
** Release Engeering team offsite, no MediaWiki train this week.
; By day
=== Week of April 29th ===
* Week of:
** 
; By day
Deployments/Archive/2019/05

=== Week of May 6th ===
* Week of:
** 
; By day
=== Week of May 13th ===
* Week of:
** 
; By day
=== Week of May 20th ===
* Week of:
** 
; By day
===Week of May 27th===
*Week of:
**Monday: US Holiday, no deploys.
;By day
Deployments/Archive/2019/06

===Week of June 3rd===
*Week of:
**
;By day
===Week of June 10th===
*Week of:
**SRE Summit - No deploys
;By day
=== Week of June 17th ===
* Week of:
** 
; By day
=== Week of June 24th ===
*Week of:
**
;By day
Deployments/Archive/2019/07

=== Week of July 1st ===
*Week of:
** No train. Thursday is a US Holiday.
;By day
=== Week of July 8th ===
*Week of:
**
;By day
=== Week of July 15th ===
*Week of:
** nothing yet...
;By day
=== Week of July 22nd ===
*Week of:
** nothing yet...
;By day
===Week of July 29th ===
*Week of:
** nothing yet...
;By day
Deployments/Archive/2019/08

===Week of August 5th ===
*Week of:
** nothing yet...
;By day
===Week of August 12th===
*Week of:
** No MediaWiki train this week, Wikimania
;By day
=== Week of August 19th ===
*Week of:
**
;By day
=== Week of August 26th ===
*Week of:
**
;By day
Deployments/Archive/2019/09

=== Week of September 2nd ===
*Week of:
** Monday Sept 2nd: No Deploys. US Holiday (Labor Day)
** Amir Sarabadani is running rebuild of item terms (phab:T225056)
;By day
=== Week of September 9th ===
*Week of:
** Amir Sarabadani (Amir1) is migrating data from wb_terms to the new term store on wikidatawiki through puppet cronjob (phab:T225056)
;By day
===Week of September 16th===
*Week of:
** 
;By day
===Week of September 23rd===
*Week of:
**
;By day
Deployments/Archive/2019/10

===Week of September 30th===
*Week of:
**
;By day
===Week of October 7th===
*Week of:
** Wikidata wb_terms item migration script running (all month)
;By day
===Week of October 14th===
*Week of:
** Wikidata wb_terms item migration script running (all month)
** October 14 (Indigenous Peoples' Day) - US Staff
;By day
===Week of October 21===
*Week of:
** Wikidata wb_terms item migration script running (all month)
===Week of October 28===
*Week of:
** Wikidata wb_terms item migration script running (all month)
Deployments/Archive/2019/11

===Week of November 4===
*Week of:
** Wikidata wb_terms item migration script running (all month)
;By day
===Week of November 11===
* Week of
**SWATers may be unavailable due to TechConf
**No Train this week due to TechConf
**Wikidata wb_terms item migration script running (all month)
;By Day
===Week of November 18===
* Week of November 18:
** NO TRAIN. Engineering Productivity team offsite (including Release Engineering).
** Wikidata wb_terms item migration script running (all month)
;By Day
===Week of November 25===
Deployments/Archive/2021/04

==Week of April 05==
======
======
======
======
======
======
======
==Week of April 12==
======
======
=== ===
=== ===
======
======
======
==Week of April 19==
======
======
======
======
======
======
======
==Week of April 26==
======
======
======
======
======
======
======
Deployments/Archive/2021/05

==Week of May 03==
======
======
======
======
======
======
======
==Week of May 10==
======
======
======
======
======
======
======
==Week of May 17==
======
======
======
======
======
======
======
==Week of May 24==
======
======
======
======
======
======
======
==Week of May 31==
======
======
======
======
======
======
======
Deployments/Archive/2021/07

==Week of July 05==
======
======
======
======
======
======
======
==Week of July 12==
* Amir is running refreshImageMetadata.php for commons on a screen in mwmaint2002
======
======
======
======
======
======
======
==Week of July 19==
* Amir is running refreshImageMetadata.php for commons on a screen in mwmaint2002 (phab:T275268)
======
======
======
======
======
======
======
==Week of July 26==
* Amir is running refreshImageMetadata.php for commons on a screen in mwmaint2002 (phab:T275268)
======
======
======
======
======
======
======
Deployments/Archive/2021/08

==Week of August 02==
* Amir is running refreshImageMetadata.php for commons on a screen in mwmaint2002 (phab:T275268)
======
======
======
======
======
======
======
==Week of August 09==
======
======
======
======
======
======
======
==Week of August 16==
======
======
======
======
======
======
======
==Week of August 23==
======
======
======
======
======
======
======
==Week of August 30==
======
======
======
======
======
======
======
Deployments/Archive/2021/11

==Week of November 01==
======
======
======
======
======
======
======
==Week of November 08==
======
======
======
======
======
======
======
==Week of November 15==
======
======
======
======
======
======
======
==Week of November 22==
======
======
======
======
======
======
======
==Week of November 29 ==
======
======
======
======
======
======
======
Deployments/Archive/2022/01

==Week of January 03==
======
======
======
======
======
======
======
==Week of January 10==
======
======
======
======
======
======
======
==Week of January 17==
======
======
======
======
======
======
======
==Week of January 24==
======
======
======
======
======
======
======
==Week of January 31==
======
======
======
======
======
======
======
Deployments/Archive/2022/05

==Week of May 02==
======
======
======
======
======
======
======
==Week of May 09==
======
======
======
======
======
======
======
==Week of May 16==
======
======
======
======
======
======
======
==Week of May 23==
======
======
======
======
======
======
======
==Week of May 30==
======
======
======
======
======
======
======
Deployments/Archive/2022/10

==Week of October 03==
======
======
======
======
======
======
======
==Week of October 10==
======
======
======
======
======
======
======
==Week of October 17==
======
======
======
======
======
======
======
==Week of October 24==
======
======
======
======
======
======
======
==Week of October 31==
======
======
======
======
======
======
======
Deployments/Archive/2023/01

==Week of January 02==
======
======
======
======
======
======
======
==Week of January 09==
======
======
======
======
======
======
======
==Week of January 16==
======
======
======
======
======
======
======
==Week of January 23==
======
======
======
======
======
======
======
==Week of January 30==
======
======
======
======
======
======
======
Deployments/Archive/2023/05

==Week of May 01==
======
======
======
======
======
======
======
==Week of May 08==
======
======
======
======
======
======
======
==Week of May 15==
======
======
======
======
======
======
======
==Week of May 22==
======
======
======
======
======
======
======
==Week of May 29==
======
======
======
======
======
======
======
Deployments/Archive/2023/07

==Week of July 03==
======
======
======
======
======
======
======
==Week of July 10==
======
======
======
======
======
======
======
==Week of July 17==
======
======
======
======
======
======
======
==Week of July 24==
======
======
======
======
======
======
======
==Week of July 31==
======
======
======
======
======
======
======
Deployments/Archive/2023/10

==Week of October 02==
======
======
======
======
======
======
======
==Week of October 09==
======
======
======
======
======
======
======
==Week of October 16==
======
======
======
======
======
======
======
==Week of October 23==
======
======
======
======
======
======
======
==Week of October 30==
======
======
======
======
======
======
======
Deployments/Archive/2024/01

==Week of January 01==
======
======
======
======
======
======
======
==Week of January 08==
======
======
======
======
======
======
======
==Week of January 15==
======
======
======
======
======
======
======
==Week of January 22==
======
======
======
======
======
======
======
==Week of January 29==
======
======
======
======
======
======
======
Deployments/Archive/2024/04

==Week of April 01==
======
======
======
======
======
======
======
==Week of April 08==
======
======
======
======
======
======
======
==Week of April 15==
======
======
======
======
======
======
======
==Week of April 22==
======
======
======
======
======
======
======
==Week of April 29==
======
======
======
======
======
======
======
Deployments/Archive/2024/07

==Week of July 01==
======
======
======
======
======
======
======
==Week of July 08==
======
======
======
======
======
======
======
==Week of July 15==
======
======
======
======
======
======
======
==Week of July 22==
======
======
======
======
======
======
======
==Week of July 29==
======
======
======
======
======
======
======
Deployments/Archive/2024/09

==Week of September 02==
======
======
======
======
======
======
======
==Week of September 09==
======
======
======
======
======
======
======
==Week of September 16==
======
======
======
======
======
======
======
==Week of September 23==
======
======
======
======
======
======
======
==Week of September 30==
======
======
======
======
======
======
======
Deployments/Archive/2024/10

==Week of October 07==
======
======
======
======
======
======
======
==Week of October 07==
======
======
======
======
======
======
======
==Week of October 14==
======
======
======
======
======
======
======
==Week of October 21==
======
======
======
======
======
======
======
==Week of October 28==
======
======
======
======
======
======
======
Deployments/Archive/2024/12

==Week of December 02==
======
======
======
======
======
======
======
==Week of December 09==
======
======
======
======
======
======
======
==Week of December 16==
======
======
======
======
======
======
======
==Week of December 23==
======
======
======
======
======
======
======
======
==Week of December 30==
======
======
======
======
======
======
Deployments/BetaNotes

== Purpose ==
To make a lua module that'll create an easy to read table of what wiki groups are upgrading on a given deployment day.
== example 1 ==
Whatever syntax helps, but one option could be...
{{#invoke:DeploymentMWUpgrade
|group0=1.23wmf9
|group1=1.23wmf8 > 1.23wmf9
|group2=1.23wmf8
|}}
to turn into
{| class="wikitable"
! group0
! group1
! group2
|-
| 1.23wmf9
| style="background-color: lightgreen;" | 1.23wmf8 -> 1.23wmf9
| 1.23wmf8
|}
eg:
group0 	group1 	group2
1.23wmf9	1.23wmf8 -> 1.23wmf9	1.23wmf8
== example 2 ==
{{#invoke:DeploymentMWUpgrade
|group0=1.23wmf9 -> 1.23wmf10
|group1=1.23wmf9
|group2=1.23wmf8 -> 1.23wmf9
|}}
to turn into
{| class="wikitable"
! group0
! group1
! group2
|-
| style="background-color: lightgreen;" | 1.23wmf9 -> 1.23wmf10
| 1.23wmf9
| style="background-color: lightgreen;" | 1.23wmf8 -> 1.23wmf9
|}
eg:
group0 	group1 	group2
1.23wmf9 -> 1.23wmf10	1.23wmf9	1.23wmf8 -> 1.23wmf9
Deployments/Blocking tasks

Each version of MediaWiki that is deployed to Wikimedia's production clusters should have a corresponding task in Phabricator. When a release-critical issue is discovered and reported in Phabricator, it should be added as a subtask under the blocker task for the most current or any other affected versions. Release engineers monitor all sub-tasks for the deployment branch they are assigned to and all serious issues must be resolved before resuming routine code deployments. 
The current train blocker task may be found via: https://train-blockers.toolforge.org
== Maintaining the blocking tasks ==
Periodically, the release manager will create batches of new tasks in Phabricator for planned upcoming MediaWiki version. 
The Release Tools Repository contains a script to make blockers
Usage: ./bin/phab-train-blocker-tasks [--count NUM] --date START_DATE START_VERSION
Example: ./bin/phab-train-blocker-tasks --count 10 --date 2022-08-08 1.39.0-wmf.24
You must provide the date and version corresponding to the first task that you will create in the series.
* The --count argument should be followed by an integer specifying how many new tasks should be created. If --count is omitted then you will only create 1 task.
* The --date argument should be followed by a date in YYYY-MM-DD format. This date should be the Monday of the week your version is being deployed.
* The last argument on the command line is the wmf version corresponding to the provided date, in #.##.#-wmf.# format.
For Example: With your shell's working directory set to the root of the release tools repo, run the following command to create a series of 2 tasks beginning with 1.31.0-wmf.14 on 2017-12-25
== Limitations ==
The blockers plugin doesn't know when one version series ends and the next begins. You have to create (for example) the 1.31.0-wmf.* series separately from the 1.32.0-wmf.* series.
== Install requirements ==
 
* python-phabricator
* a valid ~/.arcrc. 
== See Also ==
* Deployments/Holding the train.
Deployments/COVID-19

== Why ==
We want to avoid overburdening people who are single points of failure (SPoFs) who may be unavailable, leading to a broken state lasting for a long time.
== Questions to answer if you’re thinking about merging ==
* Can you roll back this change without lasting impact?
** A recovery plan is required as this will help identify our capacity for recovering from the failure
** THIS IS A KEY QUESTION, if you can’t answer it, you shouldn’t deploy
** Please ensure that if your recovery plan requires anyone besides the train conductor or patch owner, that person or team is notified and confirms availability during the deployment window. If they do not confirm availability, notify Release Engineering so that the patch can be postponed until availability is confirmed. 
* Is specialized knowledge required to support this change in production?
** Are there multiple people with this knowledge?
* Is there a way to increase confidence about the correctness of this change?
** Reviews (Design, Code, etc)
** Testing coverage (unit tests, integration tests)
** Manual testing (e.g. Beta, vagrant, docker)
== Heightened Awareness ==
Please be mindful if you have work on the train.
If you have something currently in the changelog or in master please reach out.
If for any reason you feel worried about the impact of your change you can either:
* Use the train blocker process (tl;dr: select the task for the current deployment train, then make a subtask of that train task via Edit Related Tasks… Edit Subtasks).
* Add a note on the the task for the current deployment train using the risky change template.
Please note that we are re-instigating train-blocker retrospectives to aid us in our continuous improvement efforts. Please see the retrospectives workboard for more information about existing and past retrospectives.
== Office hours ==
There will be IRC office hours in available to help with initial questions.
Mondays - 17:00 UTC
Deployments/Calendar

The deployment calendar page is generated weekly by a script that lives in the repos/releng/release repo called makedeploymentcaledar.py.
== Example Usage ==
=== Week with a train with an EU primary conductor and an American secondary conductor ===
$ ./make-deployment-calendar/deployments-calendar --schedule=European+American train --old 1.35.0-wmf.31 --new 1.35.0-wmf.32 --deployer='{{ircnick|hashar|Antoine}}, {{ircnick|twentyafterfour|Mukunda}}' --blocker-task=T249964
=== Week with a train with an American primary conductor and an EU secondary conductor ===
$ ./make-deployment-calendar/deployments-calendar --schedule=American+European train --old 1.35.0-wmf.30 --new 1.35.0-wmf.31 --deployer='{{ircnick|brennen|Brennen}}, {{ircnick|hashar|Antoine}}' --blocker-task=T249963
=== Week with a train with an American primary conductor and an American secondary conductor ===
$ ./make-deployment-calendar/deployments-calendar --schedule=American+European train --old 1.35.0-wmf.30 --new 1.35.0-wmf.31 --deployer='{{ircnick|brennen|Brennen}}, {{ircnick|hashar|Antoine}}' --blocker-task=T249963
=== Week without a train ===
$ ./make-deployment-calendar/deployments-calendar --schedule=NoTrain
=== Week American primary train conductor and American secondary conductor ===
$ ./make-deployment-calendar/deployments-calendar --schedule=American train --old 1.35.0-wmf.26 --new 1.35.0-wmf.27 --deployer='{{ircnick|longma|Jeena}}, {{ircnick|James_F|James}}' --blocker-task=T247774
=== Generate a week that is not the next week ===
$ ./make-deployment-calendar/deployments-calendar --start-date 2020-05-18 --schedule=NoTrain
== Schedules ==
* NoTrain
* American
* European
* American+European
* European+American
== Full Usage ==
usage: deployments-calendar [-h] [-c CONFIG_FILE] [-m MESSAGE] [--schedule SCHEDULES] [--start-date START_DATE] {train} ...
deployments-calendar
====================
Render the Deployments calendar for Wikitech
Example usage for weeks where there is a train:
 ./deployments-calendar \
 train \
 --old 1.34.0-wmf.18 \
 --new 1.34.0-wmf.19 \
 --deployer '{{ircnick|thcipriani}}' \
 --blocker-task T220744 \
 --schedule American
Always generates the schedule starting *next monday* -- you can pass a
more explicit start date the schedule will pickup the next monday:
 ./deployments-calendar --start-date 2019-05-01
positional arguments:
 {train}
optional arguments:
 -h, --help show this help message and exit
 -c CONFIG_FILE, --config-file CONFIG_FILE
 config json file
 -m MESSAGE, --message MESSAGE
 Messages to print at the top of the week. Can be passed multiple times.
 --schedule SCHEDULES Active alternate schedules (e.g., American)
 --start-date START_DATE
 Alternative start date for calendar, defaults to next Monday
Deployments/Emergencies

Emergency deployments happen when things need fixing right now, even though deployments aren't happening right now.
== How to ==
 🚨 Step-by-step – to do an emergency release you must:
* Join on libera.chat
* Get positive confirmation from SRE before deployment, and inform Release Engineering that you need to deploy (see the template below)
* Have someone able to deploy your change
Ways to find a deployer:
* Ask if there is someone available to deploy in on libera.chat (see the template below)
* Message and/or the person assigned to this week's train
* Include a link to the patch you'd like to deploy (and the task if appropriate)
IRC message Template
I need an emergency deploy for https://gerrit.wikimedia.org/r/1234 -- context is T1234, are SRE ok with a deployment? (cc: thcipriani [INSERT WEEKLY TRAIN CONDUCTOR NAME]). I (already have|need) someone to deploy.
== Reasons for an emergency deploy ==
* Address security issues
*: For example, a mis-configuration once meant that a private wiki and all of its content was accidentally made public.
* Avoid data loss / corruption
*: For example, a coding error meant that newly-painted pages were being cached in a corrupted form; the longer it went, the more of the site was wrong.
* Maintain availability
*: For example, a new feature proved much more popular than planned and the extra load it was causing was threatening to take down the site, so it was temporarily disabled over a holiday, until people were back at work.
* Prevent abuse
*: For example, a massive content scraping run from a search engine wasn't responding to automated HTTP 429 speed bumps and so had to be manually blocked until they could adjust their code.
* Major loss of functionality / appearance
*: For example, a code efficiency change broke the visual appearance and usability of parts the sites for a large number of logged-out users, and so the change was reverted out of production until it could be fixed.
== For deployers ==
* Rollback first, fix later; maintaining an overall service to our users is the most important focus.
* Prioritise general availability over that of new features; we have a billion readers and only a few users of your new tool, no matter how cool. 
* Make on-wiki edits rarely, and only when you really have to; each wiki's editing community expects autonomy.
Category:Deployment
Category:Operations policies
Deployments/Features Process

The WMF aims to move to a quicker release/deploy cycle with the near-term goal of moving to a weekly deploy cycle (exact details TBD). With that in mind, User:Greg Grossmeier is interviewing all WMF Feature Teams on their current development and deployment process, how it interacts with the bi-weekly deploys, how they use testing/QA in that process, and where any pain points are that might prevent them from moving to a faster cycle.
Summary of the interviews
* /General Feedback
* /TODOs
Background (very) raw notes:
* E2
* E3
* Mobile
* VisualEditor
Deployments/Features Process/E2 Notes

== aft ==
* if anything new to be deploy, matthias deploys
* weekly slots every tuesday
* if small changes that aren't urgent we wait until platform
* every change is pushed to gerrit, then to master then deployed through platform or the aft window, or sometimes with kaldari's deploy :)
* prototype branch
** not gated
** eeprototype.wmflabs
** works out decently well
** time consuming to merge back to master, keeping in sync
** betacluster could be useful if that was able to pull in a certain branch/extension
*** only master is visible on betalabs
*** maybe worth a conversation
== kaldari, benny on Echo==
* fairly similar
* if two live versions,
** we each take one for deploy
* not a strict schedule
* not using separate branches
* they keep eeprototype on master
* try pushing to master often, less than a week
* core code that sits and rots -- important
* usually ok with non-performance
* need a strong db type person who can review on core changes
* does get good updates from Chris
** Chris is pretty good proactive wise
* for performance they don't have anyone
* terry's approach is to push the envelope and push yourself if you have to, if they complain then ask them to review :)
* everything is configurable
* ResourceLoader has a hash update of css/js, gets stuck on old versions when echo pushes out, fatal problems
** go on fenari, touch, resync