Jump to content

Wikimedia Release Engineering Team/Goals/201516Q1-planning

From mediawiki.org

Possible Goals

[edit]
project people involved votes
Our Q1 Goals
Isolated CI
  • boot instances from OpenStack API
  • subset of jobs run in disposable VM (not isolated)
Antoine

Dan

Zeljko

+1+1
RESTBase Deployment tooling
  • Scope/deliverables in linked task.
Chad

Dan

Tyler

Mukunda

+1 +1
Gerrit-Differential migration

Scope:

  • Have repositories cloning from phabrcator working
  • Begin prototyping CI integration with the goal of having a proof of concept by end of quarter
Mukunda

Antoine

Chad

+1
Below the cut
CI+release for Apps (iOS and Android)
Staging (resurrect?)
  • goal: make a staging cluster that is "easily" reproducible
Chad +1
Browser Test dashboard / per team test history (resurrect?)
  • This is pretty much done
  • It could use incremental improvements (link to create new phab task, scenario 'pulse') but these don't need team-wide priority
Dan
Encourage developers to increase code coverage
  • in conjunction with TPG, this was a call out from the previous Team Health Check surveys
  • (I might have the wrong task for this, but it has the right name ;) )
  • Not sure this should be about increasing coverage specifically but about improving tooling and practices
Dan +1
Organizing release branches and SWAT requests in Phabricator / releeph..
The new faster deployment cadence
  • I (Mukunda) guess the goal here is to continue releasing fast without breaking everything constantly and catastrophically. So essentially more testing and streamlining the deployments. (See releeph)
Chad +1