QA/Meetings/2014/June 18

From The Document Foundation Wiki
< QA‎ | Meetings‎ | 2014
Jump to navigation Jump to search

(Remember: Meeting shifted to Wednesday at 17:30 UTC at the new day/time...)

Meeting of the QA Team

previous - next

Date and Time (UTC) 2014-06-18 17:30 UTC
G+ Hangout http://bit [dot] ly/LibO_QA_call_hangout
Chair Robinson Tryon
Secretary Robinson Tryon





Joel, Robinson, Jay, Sophie, Florian R.,
Bjoern, Jean, Francisco ? someone new? :-)

Talkyoo Room Number 537138


Agenda + Minutes


Content from the meeting itself ("the minutes") will be displayed in blue boxes like this.

Before we Start

A few minutes before we officially start the call, we'll try to have a few people on hand to help assist newbies set up their teleconferencing gear, get things muted, and log on to all of our communication channels:


Put start time and attendees list in the table

IRC Minutes

(Talkyoo meeting today)

The State of QA

Including any Opening Discussion

  • Impress Remote:
    • Bluetooth adapters arrived?
  • xx- Bugzilla migration
    • Updates...
    • Re: need to reset passwords
      • Email notification ahead of migration
      • Tweak the change-password page and the front page to indicate that people will need to reset their passwords
      • Create an 'About our new Bugzilla' video as a part of our 'Intro to QA' series
  • Bugzilla:
    • SUGGESTION: Use to host Bugzilla
    • We can have both LibreOffice and some of the Document Liberation Project libraries all exist as top-level products in the bugtracker
  • QUESTION: Should we refocus ourselves as the TDF QA Team (to cover LibreOffice, DLP, etc.. ?)
  • Can we get information passed from the application to the BSA via the URL?
    • Both technical and legal hurdles there (Joel)
    • Possibly just OS-detection
  • Bluetooth adapters still en-route
  • Congrats to Joren for finishing his Masters degree! (all done by the end of this week)
  • Joel will email follow-ups re: Bugzilla Migration
    • June and July will be busy for us, but we'll find a good time (hopefully!) for migration to occur.

Project Management:

  • What about global TODO lists? (across various TDF/LibreOffice teams) (Joel)
    • Perhaps something available via Redmine? Or a project management tool? (Robinson)
      • Best option for now is Wiki, but we'll still keep looking.
  • ACTION: Robinson will check-in with cloph re: project in Redmine for project management

BugHunting Session

  • Advertised on the website (Sophie)
  • Let's invite a LOT of people!
  • Try to have coverage in the IRC channel -- to answer questions for any newbies who stop by

weekly status



UNCONFIRMED bug count:

  • June 4th: 1101
  • Today: 1042
  • Difference: -59
  • ACTION: Joel will come up with strategies (bloggers? other marketing?) to get us under 500 UNCONFIRMED over the summer (by the end of August)
  • If we can do -30 to -50 a week, we'll meet our goal (Joel)
  • Excited that it's down so much
  • Keep up the good work!

Regression watch (Bjoern)

* Regressions in 4.3 not in 4.2
    • Previous Counts: 32
* Regressions in 4.2 not in 4.1
    • Previous Counts: 65

Topics for ESC?

Does anyone have any topics/concerns that I should bring to the Engineering Steering Committee (ESC)? (Robinson)

  • Still going up...
  • Hopefully we'll see that number go down after 4.3 is released

Need_Advice Bugs

NeedAdvice bugs

  • Previous counts: 80+, 32
  • Back down to reasonable number

Pending Items

Quick ACTION items:

  • [DONE] ACTION: Order bluetooth adapters for Joren, Joel, Florian R. (Robinson -> Floeff)
    • June 05 - Adapters now ordered for Joel, Joren, and Florian R.

PENDING ITEM: Auto-updates for regular users and QA Testing

  • ACTION: Investigate auto-updates for regular users and/or for QA/testing purposes (Robinson)
  • ACTION: Open discussion again re:auto-update for QA on the mailing list (Robinson)
    • Related: tdf#78592 - "LibreOffice-Installation enhancement/medium NEW UI: Provide RSS feed for torrent downloads" (Joel)

PENDING ITEM: Bugzilla Migration etc.

  • ACTION: Organize time to stress-test new Bugzilla VM (Joel)
  • ACTION: Make sure to suppress outgoing email during our testing of the test Bugzilla (Robinson)
  • ACTION: Perhaps add Simple HTTP Auth (htaccess) control restricting access to (Robinson/Norbert)
  • ACTION: Resolve url for hosting our Bugzilla instance (Joel)
    • Deal with acronym if using url (tdf# ?)
  • ACTION: Set up call and/or thread(s) with the useful people on a mailing list (Robinson)
    • May 22 - Started process
    • June - Need to follow-up again with key people re: current progress (Robinson)
  • Joel will ping involved parties

PENDING ITEM: Bibisect Repositories

  • ACTION: Chat w/Bjoern, etc... re: updates to bibisect repos (Robinson)
    • Propose docs on testing w/3.3.0 separately to place bugs in pre-LO category (Robinson)
  • [DONE] ACTION: Make combined bibisect repo available for testing (Bjoern) + Provide better docs
  • ACTION: Provide documentation for mac bibisect on wiki (Norbert)
    • Bjoern's done some work here... get update from him.
  • [DONE] ACTION: Create EasyHack to test all bugs tagged 'PreBibisect' to determine if they are also 'Inherited From OOo' (Joel)

To review:

  • IDEA: Add bibisect into regular Developer workflow
  • IDEA: Create graph/tool to show which builds contain a given commit
  • Ping Norbert about bibisect on Mac --> perhaps Redmine ticket, too
  • What about bibisect on Windows? (Bjoern)
  • Perhaps ask Cloph for help re: Bibisect stuff, and keep Norbert for Bugzilla migration (Bjoern)
    • Norbert would like to be done with Bugzilla migration (Joel)

PENDING ITEM: GUI for Bibisect

  • [SUPERSEDED] ACTION:' Florian R. will make bibisect-gui work on Ubuntu....with Joel
  • ACTION: Review BibiGUI -- any Windows/C# Python volunteer dev (Bjoern)
  • ACTION: Throw something at me [Robinson] if I forget [to poke at Python...] (Florian R.)
  • ACTION: Create an EasyHack bug for the process of rewriting the existing C# code in Python (or Java) (Florian R.)


  • ACTION: SI-GUI: Contact the people running "interesting" Windows tinderboxes and ask for their assistance (Florian R.)
  • Problem determining commit hash from build ID when working with Windows builds (Florian R.)
    • The build ID should be derived from (aka the *same* as) the commit hash

PENDING ITEM: EOL, Release series, and Stable versions

  • ACTION: We'll wait and see if the Fresh vs. Stable (esque) language ends up in the updater (Robinson)
    • May 5th - Punting to see until updater is fixed
  • [SUPERSEDED] ACTION: Joel will start a thread on the QA list where we can bring up concerns
  • ACTION: Make enhancement request for this issue (so we can take it off the agenda) (Joel)
  • Talk about it later

PENDING ITEM: Planning Regular QA Events

  • [SUPERSEDED] ACTION: Create a wiki page that mirrors our Release Plan page to try to coordinate QA events in conjunction with our release cycle (Joel)

PENDING ITEM: Daily builds for all platforms

  • [DONE] ACTION: Robinson will take point on making sure we get daily builds for win/mac/linux
  • [SUPERSEDED] ACTION: Make NAGIOS rules a priority --> very important for Windows tb for SI-GUI/Florian (Robinson)
  • Talked to Cloph, he said we didn't need NAGIOS rules (Robinson)
    • If we continue to have problems with missing builds, please let me know and we'll renew our request for NAGIOS or other automated monitoring.


  • ACTION: USA involvement in hackfests -- (Keep on the agenda, discuss on QA list) (All)
  • ACTION: Joel & Robinson will chat about Boston

Update on:

  • Potential Hackfest in Boston in July
    • State of QA Documentation?
  • Other Events: (School in Pennsylvania)?
  • US Summer Hackfest: Boston (July 26-27)
    • Joel will arrive in Boston ~9pm on Friday
  • Paucity of developers in person (Joel)
    • Possibly Mmeeks
    • Google Hangout? Remote developers?
    • ACTION: Joel will recruit a few European developers to connect remotely
  • We have other programming tasks: Involve Florian R./Bibisect GUI?
  • Having technical projects for participants is KEY
  • Bugzilla skills would be helpful (Florian R.)
  • Get QA programmers together to plan our game (Joel)
    • That would be (Robinson, Rob, Florian R., etc..)
  • Building LibreOffice in the cloud?
    • ACTION: Check on status of LibreOffice building in the cloud for hackfests (Robinson)
  • ACTION: Follow-up on what resources we have re: in-person/remote devs in 1 week (June 25) (Robinson)
  • ACTION: Include request for artists to attend the Hackfest (make sure we have enough for them to do!) (Robinson)
  • Possible Austin, TX hackfest next year
  • Charlie R. and Pennsylvania are moving along (Joel)
  • For those of you overseas -- Arnaud Versini is running a hackfest in Toulouse! Hackfest/Toulouse2014

Long-term/Frozen Pending Items

These are long-term or frozen items (i.e. on ice until something else happens) that we don't want to forget about...

PENDING ITEM: MozTrap Localization

  • ACTION: MozTrap translation (GUI and tests) continues to be high-priority for QA (Needs someone to shepherd)

To review:

  • Other project who might want to work on translating GUI w/us?

PENDING ITEM: Feedback pages

  • ACTION: Sophie will shepherd native-lang versions of Feedback page

To review:

  • Next steps for NL versions (bug #?)


  • (Future progress)

PENDING ITEM: Update the whiteboard/keywords page

  • [DONE] ACTION: Joel will work on tdf#71761 - Cleanup Whiteboard Wiki Page slowly.

Currently in progress. A sample can be seen here: Test

  • Mostly done.
  • Just a little more organization

PENDING ITEM: Most Annoying Bug List

  • ACTION: Joel will propose stricter guidelines for what qualifies as a MAB

To review:

  • How is the test going? (using the 'Priority' field in Bugzilla)


PENDING ITEM: Talk to CS Department/others at University

  • ACTION: Put up a message on the message board at his University and see who is interested (Joel)
    • Need to meet w/Charlie R. to talk with his Uni contacts as well

New Action Items

All items proposed between meetings go here

New Items (Proposed/Discussed at the Meeting)

NEW ITEM: description (your name)


  • ANNOUNCEMENT: Our next meeting will take place... July 2nd (Wednesday) at 17:30 UTC, unless otherwise noted on the QA/Mailing List.


Put meeting-adjourned time in the table


(Add topics below and reference them as #Example Topic in the Agenda/Minutes above)

Example Topic