DeveloperServices/TeamMeetings/2015-05-05: Difference between revisions

Revision as of 17:28, 5 May 2015

bkero
- Wrote partial hgweb-from-vct host installation playbook
- scan-build + mozreview
fubar
- started docs refresh
- BMO PHX→AWS planning started
- test VM for docker builds in SCL3; m-c wrangling
- bzr tarballs (hal?)
gps
hwine
- some progress on CVS
- lots of interrupts about FF 38.0 (l10n issues)
- power cycle planning
lmandel
smacleod
- Finished up git diff support in RB core
- Started on MozReview patches to switch us to new diff support
- Ran some basic usage statistics on MozReview

bkero
- Finish hgweb-from-vct playbook
- mozreview+pulse+bots interaction as prereq to implementing scan-build for gecko patches
fubar
- docs refresh con't
- SVN data
- docker build testing
gps
hwine
- Intern ramp up - welcome Anhad (irc ffledgling)
- vcs-sync
- scl3 power work
lmandel
smacleod

(hwine) Gentle reminder - any maintenance work to any of our systems should be coordinated and pre-announced in #moc. Good habit and builds good will(sm).
(lmandel) bz identified functionality (CVS attic blame) that we (as in Mozilla) have decommissioned without a replacement. From his comments, a Web based way to access blame would make him more productive. Hal has a thread on the mailing list about get bug 1155388 into the dxr backlog.
(lmandel) We talked about integrating static analysis in the review process. Sylvestre Ledru and I discussed prototyping scanbuild diff results in MozReview. Would be opt-in and look something like:
- dev requests review from scanbuild
- build with patch(es) created automatically, scanbuild run
- diff from scanbuild results with patches compared against latest m-c build or separate build that does not include patches
- diff posted to MozReview
(lmandel) Do we have best practices docs for using our tools and, more generally, how to work as a Mozilla dev?
(lmandel) Interested in giving a talk to our interns? Sign up: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=45125125
(hwine) With additional task cluster changes, we're starting to see more load & alerts on git.m.o. Seems like a good time to make a tuning push on git.m.o? We have some bug already filed, and the TC team may have input on how their use is ramping.

@@ Line 35: / Line 35: @@
 * lmandel
 * smacleod
+** Finished up git diff support in RB core
+** Started on MozReview patches to switch us to new diff support
+** Ran some basic usage statistics on MozReview
 === Planned for this week ===