We currently pass make-wmf-branch a "special_extensions" configuration which causes it to cut WMF train release branches from the wmf_deploy branch. This is unlike almost any other extension, and causes lots of confusion both within and without Fundraising Tech. We'd like to be more WMF-standard about how we deploy.

Considerations:

• We're still fond of keeping control over the master->deployment promotions, so that we can write and CR patches at a normal pace, then deploy only what we intend to.
• Must be intuitive to deployers outside of fr-tech.

@Catrope suggested one solution which we're leaning towards, but it should be discussed further, hopefully with involvement from the RelEng team. In his scheme, make-wmf-branch would cut wmf.* release branches from whatever is already deployed, and would disregard master or any other branch. In order to deploy new patches, the Fundraising team (usually us) would merge changes from master into the currently active wmf.* branch (for SWAT), or the upcoming wmf.* branch (for going with the train).

Feedback is welcome!