Wikimedia Release Engineering Team/Trainsperiment week

  🚂🧪 Trainsperiment Week March 21, 2022. Four trains. One week. Six terrified RelEngers.

What is this!?
We’re going to do four trains the week of Mon, 21 March 2022. 😬

If you have 💡 Ideas or thoughts please leave them on the talk page here.



🤔 Unknowns #
Here’s a list of things we know we don’t know. If you can help with any of these: reach out!


 * How will more trains affect caches and site performance? (T303758)
 * Are developers going to need to be more mindful of forward and backward compatibility? (T303759)
 * How will rollback work with blockers? This one is on us, but we’ll be figuring it out as we go. (T303747)
 * Will blocker tasks be too confusing with so many trains?
 * Is this sustainable?

🏆 Goals #
A shorter time between when developers write code and when that code gets live traffic is our goal. RelEng believes the benefits of that are:
 * More accurate mental model of production makes development easier
 * Creates a smaller amount of code per release, which makes the release easier to debug and test
 * Makes it easier for developers to fix bugs in a release since the context is still in their heads

📅 Schedule #
This is a one-week experiment, to gather data for possible future changes.

Mon, 21 Mar 2022 #

Tue, 22 Mar 2022 #

Wed, 23 Mar 2022 #

Thu, 24 Mar 2022 #