Wikimedia Release Engineering Team/Offsites/2018-01-Sonoma/Retro of previous offsite

greg: bubble up estimation discussion for org annual planning

 * Discussed. Point taken by both Victoria and the rest of tech-mgt. Seemed to be how other teams were experiencing the world as well.
 * ✅ by the letter, but by the spirit?

JR: reach out to Google for help with Code Health meetings

 * this stuff may be Google-specific
 * delicious secret sauces
 * What did you learn trying to put this together
 * JR Having lunch with Google Code Health Lead on July 12th

JR: Code Health Dashboard

 * Ask code health group what belongs on the dashboard
 * Talk with analytics about this
 * Long term storage of jenkins artifacts (elastic search?)
 * Investigate options for code complexity and coverage

Greg: Phame blog for techblog content

 * We (RelEng) should write up a "why we're turning it back on" as the first new post from the "Doing the Needful" blog. tl;dr: Tech-mgt wants a place to share technologist focused blog posts. The Wikimedia Blog is not it (it is the wrong audience and the process is too heavy weight). This meets our needs easily and is low cost (as in person time).

Greg (and Chad, Mukunda, Tyler): JFDI the changes to deploy branch cutting and train cycle
Discussed at team offsite. Let's finally just put the branch cut on a timer. And, at the same time, let's make any changes to the deploy cycle/cadence and use of Beta Cluster that would benefit from such a timer (eg: cutting on Thursday, deploying to a multiversion'd  (or whatever) over Friday and the weekend for E2E and manual testing.
 * , should be reprioritized

(Added) Roadmap for Code Health (Group)

 * See Wikimedia Release Engineering Team/Offsites/2017-05-Vienna.