Wikimedia Release Engineering Team
|
Release & QA
Release Engineering and QA. Working to improve the quality of code and reduce the time users get it.
|
This is the team responsible for Release Engineering/Management and QA at the Wikimedia Foundation. We predominately use the QA mailing list along with conversations on the appropriate IRC channels (especially #wikimedia-tech connect, #wikimedia-operations connect, #wikimedia-qa connect, and #wikimedia-dev connect).
Status
Template:Wikimedia project status lineTemplate:Add new Wikimedia engineering project status update
Quarterly Reviews
Backlog/Wishlist
We maintain a list of projects that would be great to have done, but are not on our roadmap in in the near term. See the wishlist here.
Meetings
See /Meetings for notes from the Showcase meetings of the Release and QA Team.
Quarterly Progress
Feb - Apr '14 Goal Progress
See the WMF Engineering 13-14 goals page for the yearly view.
- Process through all (useful) pain points from the Dev/Deploy review session (Greg)
- Scap incremental improvements
- 1) Refactor existing scap scripts to enhance maintainability and reveal hidden complexity of current solution (Bryan)
- 2) create matrix of tool requirements per software stack (MW, Parsoid, ElasticSearch) (Greg)
- 3) Use above matrix to add/fix functionality in scap (or related) tooling for ONE software stack, prioritized by cross stack use (Bryan)
- Use the API to create test data for given tests at run time. (Jeff, Chris, Željko)
- Create the ability to test headless (Željko, Jeff, Chris)
- Run versions of tests compatible with target test environments (Chris, all)
- Make database(s) in Beta Cluster emulate production (set up db slaves) (Antoine)
March Goal Progress
Greg
- Process through pain points Status: in-progress
- security patches Status: Done
- LD SWAT team Status: Done
- next...
- LD SWAT team
- Kick off Status: in-progress
- PushBot? Status: Done - NO (without more dev than Greg can provide right now)
- create blockdiag version of flow chart Status: Done
- Refine deployment system requirements with Bryan Status: in-progress
- quarterly post-mortem kickoff Status: in-progress
- scheduled, 3/19 Status: Done
- set up morgue? Status: Not done
Antoine
- Status: In progress Fix up VisualEditor browser tests and make it voting in Gerrit
- Status: In progress Makes CirrusSearch browser tests voting
Done Publish sphinx documentation (use jenkins jobs). Examples:
- Status: In progress Migrate beta cluster from pmtpa to eqiad!
Reedy
Bryan
- Status: In progress Scap refactor/python port
- Done Extract common logic for making a command line interface into a class
- Done Fixed sync-wikiversions to use common dsh arguments
In progress Setup test environment in beta (carried forward from Feb; harder than I'd hoped)- Continue to enhance and simplify scripts
- Status: In progress Next generation deployment tooling
- In progress Organize requirements into wiki page (carried forward from Feb; pairing with Greg)
- Status: In progress Support train deploys
- Done Deploy 1.23wmf16 to group1
- Done Deploy 1.23wmf17 to group0
- In progress Deploy 1.23wmf17 to group1
- In progress Cleanup old l10n cache files on cluster
Andre
- (With Guillaume) Lead the community discussion about the shortlist of candidates for Project management tools/Review (based on Project management tools/Review/Requirements), take the first implementation steps (possibly in Labs). Status: In progress
- (With Guillaume) Have an IRC office hour about Project management tools Status: Done on 2014-03-28
(With Guillaume) Set up and facilitate the community RfC about Project management tools, and bring it to a decision.Status: Not done -- postponed to April- (With Quim) Reboot Annoying little bugs based on Google Code-In experience; Bugzilla's easy keyword; exposing an easy "bug of the week":
- Kill curated list on the wikipage; provide specific Bugzilla queries and "getting started" instructions for each area: Status: Done on 2014-03-07 (diff)
Introduce "Bug of the week" after talking to teams?Status: Not done - postponed to Q2/2014
- Better Bugzilla taxonomy: Discuss using classifications in Bugzilla and identify some initial non-controversial changes. - bugzilla:38990. Status: In progress; first smaller cleanup steps about "Tools" and deprecated stuff are
bugzilla:57738, bugzilla:54063, bugzilla:53986#c15, bugzilla:55351#c4, bugzilla:62386, bugzilla:62384; Proposal to use Bugzilla classifications on 2014-03-10 - Bugzilla setup / code:
Provide a NEEDINFO flag in Bugzilla - bugzilla:36064. Status: In progress: (porting more complicated as bmo will skip 4.4) -- might get postponed to Q2/2014- Provide a way to mark an item as NEEDINFO in Bugzilla - bugzilla:36064. Status: In progress: Created list of pros and cons of two implementations on 2014-03-10; next step is start broader discussion on wikitech-l@ and agree on which way to do
Install component watching extension to be able to receive bugmail for specific product/component for devs and triagers, plus no more manual adding of people to auto-CC by admins- bugzilla:37105. Status: Not done -- database issues when testing; not yet tested on 4.4 and upstream code is still 4.2 only. Porting more complicated as bmo will skip 4.4 -- postponed to Q2/2014
Chris
Continuing from Feb:
- Test and announce general availability of feature to check for ResourceLoader upon page load: ResourceLoader error checking more globally. Status: In progress
- Test and announce general availability of feature to use the API to create wiki pages and users: create-page (and create-user) API. Status: In progress
- Investigate how release branches are described in make-deploy-notes Status: In progress
Rummana
Željko
February Goal Progress
Greg
- Process through pain points Status: in-progress
- security patches Status: Done
- Kick off LD SWAT team Status: Not done
- next...
- create blockdiag version of flow chart Status: Done
- Refine deployment system requirements with Bryan Status: in-progress
- quarterly post-mortem kickoff Status: Not done
- set up morgue?
Antoine
- Status: In progress Complete integration of browsertests for VisualEditor
- One build worked and triggered two successful scenario!!
- Parsoid is stopped by the job now, was not previously :/
- Done Integration of browsertests for CirrusSearch. Cause me to slightly rethink the browsertests infra to closely match production.
- Done Train Zeljkof on Jenkins Job Builder script
- Zeljkof started on it. Will pair with him to finish up.
- Zeljkof found his way through JJB arcanes \O/
- Done Help migrating Cloudbees Jenkins template to JJB YAML templates
- Zeljkof started on it. Will pair with him to finish up.
- Zeljkof found his way through JJB arcanes \O/
Reedy
Bryan
- Status: In progress Scap refactor/python port
- Done Local test environment in a MW-Vagrant instance
- Done scap converted to python
- Done scap-1 converted to python
- Done add detailed duration timing for scap & scap-1
- Done remove external script dependencies from scap-1
- Done add progress bar for dsh commands
- Done Scap logs in json format for easy parsing
- Done Scap logs sent to florine via udp2log
- Done Scap logs sent to logstash via udp2log
- Done Converted mwversionsinuse to python
- Done Deleted obsolete scripts: scap-1, scap-2, find-nearest-rsync, scap-old
- In progress Setup test environment in beta (will pair with Antione)
- Continue to enhance and simplify scripts
- Status: In progress Next generation deployment tooling
- Done gather requirements via etherpad and Ops-l mailing list
- In progress Organize requirements into wiki page (will pair with Greg)
- Status: In progress Support train deploys
- Done Deploy 1.23wmf16 to group0
Andre
- (With Guillaume) Lead the community discussion about the shortlist of candidates for Project management tools/Review (based on Project management tools/Review/Requirements), take the first implementation steps (possibly in Labs). Status: In progress
- Prepare Bugzilla upgrade to 4.4 (and move to new datacenter) - Status: Done. Outstanding steps from bugzilla:49597:
- (With Daniel and Sean) Switch database and DNS from old kaulen server to new zirconium server. Status: Done on 2014-02-13
- Show common queries on Bugzilla frontpage - bugzilla:22170. Status: Done on 2014-02-13
- Finalize Bugzilla etiquette draft. Status: Done - 2014-02-05: Announcement
- Further small patches after 4.4 upgrade (License headers and template processing cleanup;
numerous contributed Gerrit patches waiting). Status: In progress - (With Quim) Reboot Annoying little bugs based on Google Code-In experience; Bugzilla's easy keyword; exposing an easy "bug of the week":
- Cover common "getting started" questions: Status: Done added on 2014-02-18
- Improve Bugzilla queries on Annoying little bugs to show a good subset: Status: Done on 2014-02-18
- Add guidelines for triagers how to identify a bug report that is good for this audience: Status: Done by editing the "easy" keyword description on 2014-02-24
- Retriage existing bugs with easy keyword: mostly Status: Done
Chris
- Investigate how release branches are described in make-deploy-notes Status: In progress
- Investigate using ResourceLoader error checking more globally. Status: Done
- Refactor tests to use the create-page (and create-user) API. Status: Done
Željko
Jeff
Rummana
| Dec '13 - Feb '14 Goal Progress | ||||
|---|---|---|---|---|
Dec-Feb Goal ProgressSee the WMF Engineering 13-14 goals page for the yearly view.
Monthly Goal ProgressFebruaryGreg
Antoine
ReedyAndre
Chris
ŽeljkoJeff
Rummana
|
Check-ins
These are here just for historical reasons, we no longer use this format.
- /Checkin-20131202
- /Checkin-20131119
- /Checkin-20131105
- /Checkin-20131008
- /Checkin-20130924
- /Checkin-20130917
- /Checkin-20131022
- /Checkin-20130910
- /Checkin-20130903