Since we're still struggling with Git, Gerrit, and figuring out the
new work-flow, Sumana asked me to hold a triage on the the issues
people have filed in Bugzilla and then write this follow-up report.

I used the open blockers on #22596
(https://bugzilla.wikimedia.org/showdependencytree.cgi?id=22596) to
guide the triage.  Chad wasn't able to be in IRC at the time, but he did
update the etherpad (http://etherpad.wikimedia.org/BugTriage-2012-03)
and Bugzilla afterwards.

http://bugzilla.wikimedia.org/33773: [TestSwarm] fetcher need git
    support

    Antoine had filed this bug but had since decided to just use
    Jenkins to push new code to testswarm. WONTFIX'd.

http://bugzilla.wikimedia.org/34141: Integrate Jenkins with Git

    Antoine said that this is (after his current focus on 1.19) his
    highest priority and he will be focused on it.

http://bugzilla.wikimedia.org/34426: installer: ability to override
    LocalSettings.php filename

    Antoine made the following note on the bug (which is mostly a
    placeholder for himself):

        I am going to need this in Jenkins to setup a local fetch out
        to be able to use multiple databases backend.

        The fix is easy to handle and not that much needed till we
        start having tests against MySQL / postgre backends which are
        not high priority.

http://bugzilla.wikimedia.org/34349: Triage Git conversion issues wiki
    pages

    Sumana made this -- turning issues noted on the wiki into Bugzilla
    issues so that they would be easier to track -- into a TODO for herself

http://bugzilla.wikimedia.org/35144: Autolink to new Gerrit / Git
    changesets and SHA-1 commits

    Chad has updated bugzilla to support links to "gerrit #XXX".
    We'll probably want to update it further to support Gerrit's GIT
    ids following RobLa's suggestion:

        The Gerrit UI seems to prefix Git ids with a capital "I", even
        offering a button for copying the full SHA-1 hash to the
        clipboard prefixed with the "I".

    I plan to set up a Labs instance of Bugzilla -- which we need to
    do to enable puppetizing Bugzilla -- so I'll have a chance to look
    at other Git links then.

http://bugzilla.wikimedia.org/35145: Make git-review more easy to
    install on Windows

    Although we have some contributors who use Windows, this isn't a
    blocker for them, so we lowered the priority.  We do want to make
    sure that new contributors are able to use Gerrit, though, so this
    will be something we are interested in.

http://bugzilla.wikimedia.org/35460: Need commit notes to match SVN
    revision numbers for core

    Chad writes:

        refs/notes/commits has information regarding the original SVN
        commit info. This is correct and in place for SVN extensions,
        but I messed it up for core. It's not super-high priority, but
        I don't know if anyone other than me can do it.

http://bugzilla.wikimedia.org/35462: Tell git on gerrit.wikimedia.org
    not to generate spurious terminal sequences

    Antoine said that Marcin could work on this.  Marcin confirmed
    that he would try to track this down, so I assigned it to him.

http://bugzilla.wikimedia.org/35469: Let LocalisationUpdate fetch from
    Git

    An update to this script was deployed by operations.  When we
    checked during the Triage, though, it wasn't working.  Roan
    tracked this down and commited a fix.

http://bugzilla.wikimedia.org/35497: Two-way syncing between Gerrit and GitHub

    Since I'm currently working on a way to merge patches from
    Bugzilla to Gerrit, I don't think this would be too much trouble
    to add once I have that working.  Anyone else who wants to
    integrate GitHub or Gitorious before I get to it should feel free
    to, though.

http://bugzilla.wikimedia.org/35429: Setup external git mirrors/clones

    Chad said that "It should be pretty easy--gerrit has built-in
    replication we can use."

http://bugzilla.wikimedia.org/35508: List of Gerrit users

    After some discussion during triage, Sumana clarified this
    request:

        This request is for us to hack something by generating a user
        page based on the Gerrit database, per the instructions in
        https://groups.google.com/group/repo-discuss/msg/c426b6a83400b58e

http://bugzilla.wikimedia.org/35510: Make Gerrit project list more
    discoverable and available

    We'd like to get the scrape this data from the UI.  Chad gives a
    pointer in the right direction if anyone wants to tackle this:

        Something working from
        gerrit.wm.o/r/gerrit/rpc/ProjectAdminService should do.

http://bugzilla.wikimedia.org/35455: Change Gerrit database schema to support 
utf8

    Supposedly, this would come out of the box if we used PostgreSQL
    or the embedded H2 database backend, we would get this
    out-of-the-box.

    Chad thinks this is silly and thinks he can change the collation
    without an issue.  He'll test his theory soon.

http://bugzilla.wikimedia.org/35531: Send email notifications of all
    MediaWiki commits to mediawiki-cvs list

    "Trivial -- someone just has to play with the hooks"

http://bugzilla.wikimedia.org/35532: Include unified diff in gerrit
    email notifications
http://bugzilla.wikimedia.org/35533: Include link to unified diff in
    gerrit notifications

    Chad says an upstream change is required for these two fixes.

http://bugzilla.wikimedia.org/35534: Implement a way to group related
    commits (allowing a commit to be in multiple groups)
http://bugzilla.wikimedia.org/35535: No way to mark merged commits as
    needing fixing

    Again, Chad says this is an upstream request to allow free-form
    tagging.

http://bugzilla.wikimedia.org/35537: Commits from the l10n-bot should
    be merged immediately (automatically)

    Chad's on this--high priority

http://bugzilla.wikimedia.org/35538: Commits from the l10n-bot
    shouldn't create too much spam

    We don't know of a clean way around this right now for e-mails yet
    (suppress e-mail via hook?), but we can easily skip IRC stuff with
    some minor tweaks to the hooks.

Thank you to all participants!

-- 
Mark A. Hershberger
Bugmeister
Wikimedia Foundation
[email protected]

_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to