Hi all,
here are the minutes of the LibreOffice QA call is on 2012-05-18 14:00 UTC.
attending: Markus, Florian, Rainer, Petr, Bjoern
pending action items:
- Update/Create active triagers wiki page (Cor/Rainer)
- collect further ideas for spending a dedicated resource (Cor/Rainer)
- blocked on CC/Litmus choice availability
- write update scenario testcase in Litmus/MozTrap (Kendy)
- bulk change remove EasyHacks in summary, make that white board only
(Rainer, Florian, all)
(actually not possible in bulk, so lets crowdsource this: when you come
across a bug with EasyHack in title, please remove it there
- Set Cor up with the Community/Forum maintainers at the distros
to better propagate Hackfests, Bug Hunting Sessions etc.
RedHat, Debian, Gentoo still missing
- send a proposal for liberal assigned use in NEEDINFO to Rainer for review
(Bjoern)
- create a QA EasyHack Gather own bugzilla requirements (Bjoern)
- create a wikipage with what we have so far and link to it (Rainer)
- blog about bug verification (Bjoern)
- bibisect: update docs (Bjoern)
completed action items:
- MozTrap evaluation install (Bjoern) - obsolete
+ blog about QA EasyHacks (Cor/Bjoern) - done by Cor, need repetition of
course
+ blog about daily build changes/bugs/features from git log (Cor)
- add EasyHack for bugzilla-twitter integration (Bjoern)
- bibisect: also rebuild the old ~50 3.5 bibisect installs for the next
update (Bjoern)
- obsolete, just needs libjpeg62 package installed on precise
structured manual testing:
- Yifan had good progress setting this up (Petr)
- account creation still creates some issues
- still might be ready as soon as next week
bug wrangling (Rainer):
- bugzilla twitter integration
- bugzilla git integration might be a blueprint (Markus)
- EasyHack: https://bugs.freedesktop.org/show_bug.cgi?id=50096
- assigning policy: really assign or CC? (Petr)
- CC is better, dev can then self-assign
AA - update bugwrangling docs to say CC instead of assign (Rainer)
- some confusion about the use of new components (Rainer)
- seems to be a better way to distrubute bugs to devs as teams grow
- (assigning to one dev isnt that helpful anymore then)
- likely a good topic for our own bugzilla, not worth it earlier (Bjoern)
AA - bring topic back to ESC (Rainer, Petr, Bjoern)
community building/communication (Cor?)
AA+ add yourself on openhatch.org (all)
- mark yourself as a mentor for LibreOffice too
- QA mentoring (Florian)
- EasyHacks seem to work great in dev, we should get something similar for
QA
- How do we find/identify mentees?
- twitter integration might get blood in the project, but here we need
those
who did some verifications/confirmations to take them to the next level
- once we have our own bugzilla we should have a Wanna meet the
QA-team-link
to the QA-List in the header/footer
- QA-List is freedesktop/hasslesome (Florian)
AA+ - Invite active bugwranglers to next call/QA list, CC Rainer (Bjoern)
bibisect for 3.5 release branch and 3.6 master (Bjoern/Korrawit):
AA - merge 3.5 and 3.6 in one big bibisect repo (Bjoern)
- should be done with the next update, likely around 3.6 branchoff
- having bibisect in a PPA for automatic updates would be nice (Florian)
- investigate bibisect in a PPA (Bjoern)
The next LibreOffice QA call is on 2012-06-01 14:00 UTC.
As always comments and additions welcome.
Best,
Bjoern
--
Unsubscribe instructions: E-mail to projects+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted
