minutes of ESC face-to-face ...

* Completed Action Items:
    + switch to pure sidebar mode in master - but not enabled by
      default, except in Impress (Caolan)
    + get kendy ssh access to production gerrit (Norbert)
    + Caolan's small gerrit patches merged

* Pending Action Items:
    + push new default templates in & fix if necessary (Ahmad)

* Release Engineering update (Cloph)
    + 4.1.2 RC2 status
        + release scheduled during the conference.
        + perhaps an announce - pending marketing
    + 4.0.6 RC1 - week after the conference Sept 30th.

* GSOC update
    + assessments ASAP ...

* QA update (Robinson)
    + Joel fixing everything in Robinson's absence.

    + https://bugs.freedesktop.org/page.cgi?id=weekly-bug-summary.html
        +160 -151 (+9 overall)
         many thanks to the top six bug squashers:
             Joel Madero 16
             Maxim 14
             tommy27 8
             Jean-Baptiste Faure 7
             Caolán McNamara 6
             ign_christian 6

    + recruiting QA triage guys going well (Robinson)
    + should we have a top confirmers stat ? (Michael)
        + bit tough to work out the top triagers
        + can build some perl to dump that here if someone can come up
          with a query (Michael M)

* ESC meeting:
    + should we move it earlier ? (Caolan)
  + no: US-ites (Kohei, Norbert)

* ABI issues (Stephan)
    + what was the status (Norbert)
    + agreed with 4.1 - just evolve stuff as it comes up
        + try not to do it in micro (as per date-time)
    + try to get larger changes in earlier in the cycle.
    + specific API query around 16 vs 32 bit API / string offsets (Norbert)
        + cost vs. benefit - should we do it at all (Stephan)
        + un-used public API by mistake: cleanup without much fuss
        + wider stuff DayTime / people experience breakage => need
          to discuss that first (Stephan)

* QA (Robinson)
    + Florian R, Bjoern - round-table later, future of QA
    + Joel & Joren - both back at school
    + recruiting & retaining people is a priority.

* tinderbox status
    + missing 'make check' tinderbox
    + can TDF provide something here ?
    + Windows was complicated - needing hardware (Norbert)
AI: + get Cloph a VM / instructions to install on TDF hardware (Markus)
       + requires a new gcc / clang version etc. gcc 4.8 etc.
    + Mac tinderboxes
       + are there any building vs. the mac baseline ? (Stephan)
       + Cloph found the trick to do this, now building with the
         right SDK (Norbert)
    + Windows tinderboxes, need to switch to MSVC 2012 - SP1
      to target XP
AI: + mail everyone wrt. instructions on how to un-break
         MSVC 2012 wrt. XP (Markus)

* release builds (Norbert)
    + propose continue doing 10.6 for 32bit, and 10.8 for 64bit
    + more and more SDK pieces are harder and harder to get to
      work on old releases
AI: + switch to 10.8 baseline for 64bit (Norbert)
    + ultimately, gerrit will do both with DavidO's help

* bibisect repository pieces
    + Windows bibisect - install into a repo
    + putting MSIs in the repo is not quick (Robinson)
    + can we just use instdir for Windows (Stephan)
        + just up-load / git checkin the instdir.
    + builds should be done from clean (Michael S)
    + resource needs for bibisect repo compression:
  + 32Gb of RAM, 8 cores - 5-6 hours doing a
    git gc --agressive
  + 1.5Mb / release - 1000 builds etc.
    + gandalf free mostly, could use that (Markus)
    + if we can work on the compression weekly - we
      can save time (Norbert)
    + ... long discussion on the workings of git ...
    + what's the most optimal window (Robinson)
        + best to re-compress up-loaded builds (Norbert)
        + we wind up with dailyish builds, perhaps 1-3 per day.
AI: + setup infrastructure to build repos (Cloph / Bjoern / Norbert)

* mail firehose discussion (Bjoern)
    + stats for mailing lists - number of mails going down
    + normalised for shut-down gerrit firehose
        + used to send mails as-if-from committer
        + and sent a mail for every commit.
    + should we re-enable the fire-hose (no)
    + should we CC the mailing list on the Easy Hacks ?
        + digest is annoying (Lionel)
        + get full comment.
AI: + CC all developers' mailing list on all the easy hacks (Bjoern)
    + gerrit digest does anyone read them ? (Stephan)
        + ~no-one really reads them
        + people should subscribe to continue to get
    + proposed easy_hack tag ? (Cor)
        + in favour of removing it - puts people off (Markus)
            + seen lots of de-motivating things
        + proposed easy hacks makes sense (Lionel)
            + should change the name so easy-hack does
              not show up, to avoid searching (Markus)
AI: + change wiki page to eliminate proposed easy hacks (Bjoern)
AI: + propose different name for proposed easy hacks (Markus)

* testing / metrics
    + automatic document load / crash regression suite (Markus)
        + Fedora 19
        + produce a VM for document load/crash testing
        + is it reliable ? (Michael)
           + few cases in headless mode / race-conditions
           + 3-4 cases per run out of 30k documents
     + takes two days to get to run.
AI: + produce a VM for this (Cloph / Markus)
        + with bibisect we could script finding the commit (Bjoern)
  + Need to extend it to export test
        + running it once per month with the coverity run (Markus)
        + can we partition the document test loads and run
          them on tinderboxen (Norbert)
AI: + do
    + callgrind / performance regression testing box
  + on Cloph's plan
AI: + produce a VM with callgrind metrics (Matus)
    + coverity automation / exports
        + what if fix is still there marked 'resolved' after
    several months is it still a bug ?
           + yes (Markus)
AI: + attempt export from Coverity categories of
          non-security critical bugs (Caolan)
           + eg. memory leaks / exception pieces.

* documentation website (Lionel)
    + docs website should have API docs for each minor release
        + API doc generation automation
        + currently run from time to time, make odk & up-load the files
        + index.html is not generated
AI: + transition and automate this inside a VM for Cloph (Lionel)

    + website proliferation: api.libreoffice.org, opengrok, etc.
        + good idea to hack the footer to link the other pages
        + eg. gerrit - link IRC channel in the footer.
        + doc sites are scattered ...
        + api.libreoffice.org - is a user/extension resource (Lionel)
  + good to do some analytics research (Thorsten)

* Questions *

* do developers have a good overview of bugs filed vs. their module ? (Cor)
    + Thorsten's take: subscribed to the fire-hoses, and German + English
      user mailing list, filter keywords & dump the rest.
    + last time: do we want to CC developers on issues (Stephan)
        + in general, important to raise awareness of interesting
    issues
            + subscribed to the bugs mailing list, and browse by title.
            + hard to filter on topic
    + hands-full with bugs CC'd on (Lionel)
        + not looking for others generally.
    + concern is that developers may overlook things (Cor)
    + bug review based primarily on topic and is seasonal (Kohei)
        + this month dealing with calc core issues eg.
    + gets all launchpad + local bugs (Bjoern)
        + not looking at one component or topic, only at most heated bugs
    + wondering about launchpad integration (Miklos)
        + do bugs auto-close ?
        + no - but launchpad has two bug states tracked.
    + should we do more categorisation (Robinson)
        + better to be able to have a dashboard (Caolan)
              + daily bug details / breakdown etc., tinderbox
                build status etc.
        + be great to have a straightforward, reproducible
          crash category
    + Cor spends lots of time improving summaries: really
      useful work, "comment #30 is the real bug"
    + good bug summaries are really useful to have (Bjoern)
    + only one fix per bug - 30 comment bugs are a disaster (Caolan)
        + everyone thinks it is their bug.
        + open a new bug - and reference this one.

* QA stats:

* Open 4.2 MAB
        + 2/8 1/6 1/6 2/6 5/6 5/6 6/6 7/7 2/2 2/2 1/1
        + https://bugs.freedesktop.org/show_bug.cgi?id=65675
* Open 4.1 MAB
        + 15/96 14/93 12/91 14/91 17/89 15/85 15/81 13/77 8/68 11/64 3/55 7/52
           16% 15% 13% 15% 19% 18% 19% 17% 12% 17% 5% 14%
        + https://bugs.freedesktop.org/showdependencytree.cgi?id=60270&hide_resolved=1
* Open 4.0 MAB
        + 56/195 54/193 55/194 52/183 50/180 52/180 44/171 32/157 14/138 13/137
           29% 28% 29% 28% 28% 29% 26% 20% 10% 9%
        + https://bugs.freedesktop.org/showdependencytree.cgi?id=54157&hide_resolved=1

* Bibisected bugs open: whiteboard 'bibsected'
        + 34/14234/141 34/140 35/140 36/167 37/137 41/137 33/128 33/125 34/124
                + http://bit.ly/VQfF3Q

* all bugs tagged with 'regression'
        + 374(+7) bugs open of 2034(+27) total
        * ~Component count net *
                Writer - 104 (+1)
           Spreadsheet - 54 (+3)
           Libreoffice - 46 (+2)
          Presentation - 31 (+3)
               Crashes - 27 (-3)
              Database - 22 (+2)
               Drawing - 18 (+0)
               Borders - 17 (+0)
             Migration - 3 (+0)
                 BASIC - 2 (+0)
    + http://bit.ly/15mM2Yn - for devs ( no NEEDINFO / UNCONFIRMED )
        + https://bugs.freedesktop.org/buglist.cgi?keywords=regression%2C%20&keywords_type=allwords&resolution=---&query_format=advanced&product=LibreOffice&list_id=36764
        + Migration: https://bugs.freedesktop.org/showdependencytree.cgi?id=43489&hide_resolved=1