BMO/Meetings/2013-08-27

Kyle, dkl, mcote, glob, AutomatedTester, lizzard, gerv

Discussion of moving Bugzilla and BMO from bzr to git. Issue, some people use package builds and rely on the latest from a particular branch. glob says people don't tend to use packages. We advise people not to. mcote says he means the tarballs they produce for downloads. glob: the standard upgrade path is a tarball which includes a .bzr file. We could do the same thing with git. new users won't have a problem but existing installs will. there will also be patch files . What if we just stop distributing the .bzr file. There may be a tinderbox problem, hosting problem.

We wouldn't shut the bzr repo for a year or so.

Extra discussion of how the cvs repo is still running. Frederic uses it, for one. gcc bugzilla uses the cvs bugzilla, and is now on 4.4. [LpSolit: 4.4 doesn't exist on CVS. GCC Bugzilla now uses bzr thanks to an upgrade from RHEL4 to RHEL6 (bzr couldn't be installed on RHEL4 due to a too old version of Python).]

Will we use github or mozilla git? mcote will investigate and clarify.

Cookies and review board. mcote is running into some issues with how BMO handles cookies.

Mozilla skin. Mostly positive reactions (lots on twitter) There are a few issues with tabzilla, dkl is working on a patch for it.

User profiles launched, looks nifty. mcote asks for there to be more data that summarizes activity in a time range. There are some other tweaks to add to it, and somewhat better explanations of each field.

Could we add that activity over time ranges with Kyle's public elastic search capability?

mcote is going to do code review for kyle's project, https://github.com/klahnakoski/Bugzilla-ETL/blob/master/src/python/parse_bug_history.py

mcote is now going to the DevOps meeting on Mondays at 12:30 PT in jakem's vidyo room.