> On 06 Oct 2016, at 17:04, Michael Meeks <michael.me...@collabora.com> wrote: > > * Present: > + Sophie, Andras, Caolan, Heiko, Markus, Miklos, Olivier, Xisco, > Eike, Norbert, Stephan, Armin, Sweetshark, Kendy > > * Completed Action Items: > + connect Xisco/JanI with Madrid GNOME guy (Bubli) > thanks, no response yet. > > * Pending Action Items: > + enable linux / system library checker on CI (Norbert) > [ pending ] > + simplify & cleanup broken Windows build instructions & test (JanI) > [ in progress ] > + align release dates and issues, patch merging (Caolan, Cloph) > [ waiting on AOO decision ] > + poke at MSDN licenses (Michael) > [ still chasing this one ] > + investigate a cron job that queries & auto-merges (Norbert) > [ waiting to see David's solution get up-stream, should be > straightforward > enough; a query and a script. ] > + tweak UI and get LiveConnect API key / build case for board (Christian) > + still need to get API key, rest is done > [ planned for 5.3 release ] > > * Release Engineering update (JanI) > + < missing JanI > + Just for reference, I did try to connect but was unable to, and wrote that on IRC, and as is evident I did fill out the minutes.
Have a nice weekend rgds jan I. > + 5.2.3 RC1 (janI) > + scheduled 25 October > + 5.1 → 5.1.6 rc2 (jani with help from Cloph) > + scheduled 18 October > + 5.3 → 5.3.0 alpha 1 Oct 18th > + Nov 21st - with the branch-off (Cloph) > + Android & iOS Remote (Cloph) > + query wrt. F-Droid maintenance ? (Stuart/Kendy) > + Windows Server 2016 (Cloph) > + should we bump our base-line to this ? > + did we decide that ? ... > + gtk 3.22 claims long term stability > + if gtk3 is enabled, make that the minimum version ? (3.20 in > practice for build-your-own support reading ifdefs) > + what consequences would there be to adding gtk3 3.22 support to the > official builds > - already enable system-cairo for gtk2 I think > > * Documentation (Olivier) > + New contributor: Andrea Mussap for Help Content > + Good cleanup work from Gabor Kelemen and Andras Timar in the > HelpContent, droping unused entries > + Blog posts for documentation > - interview (Tuesday) > - Community week (today) > + Further work in documentation.libreoffice.org > > * UX Update (Heiko) > * needsUXAdvice at Oct-06, Total number: 475 (-8) > Base 1 > Calc 35 (+1) > Draw 67 > Extensions 0 > filters and storage 1 > framework 1 > Impress 25 (+1) > Installation 0 > LibreOffice 255 (-5) > Localization 0 > Printing and PDF export 1 > UI 16 > Writer 73 (-3) > + unconfirmed ticket count down to 10 > * Hot topics for UX call tomorrow > + Allow toolbars in full-screen mode ? (tdf#95462) > + Clear direct formatting in context menu (tdf#102915) > + some people wanting it back. > + Unifying document attributes (Michael) > + lots of good things in the 'shell' etc. > + File menu override issues on Mac; thoughts appreciated > -> Ticket please against ux > > * Crashtest update (Caolan) > + 3 import failure, 1 export failures > + numbers up but small; and related to recently added asserts > + another run in progress now; expected to drop to zero in a few hours. > + Coverity still going down: > < 29 coverity issues > > * Crash reporting (Markus) > + http://crashreport.libreoffice.org/stats/ > + check it out - lots of crashes: around 1500 per day. > + cf. Firefox - millions ? > + many are odd shutdown crashes; sometimes getting into an OGL path. > + not figured out why. > + at least one serious memory corruption in VCL. > + please poke numbers from time to time & check if there is a crash. > + filtering would be great (Michael) > + can we mention it in dev-central ? (Miklos) > + can add it there. > > * UI testing (moggi) > + more or less ready in master > + two issues currently blocking: pyuno bug and one race condition > + a random assert triggered. > + people can start adding UI tests > + currently writing a tutorial on that. > + tests run OOP in python. > + connects to a small VCL / introspection piece > + support for manu UI objects is built-in, added for most > of the used VCL objects. > + easy to add support for un-supported elements. > + make uitest.uicheck > + planning to move some around to other places eg. make sc.uicheck > + tested on Linux & Windows. > + works similar to crash-testing, with bits taken from python tests. > + any input from UX for UI tests? (Heiko) > + purely developer tests just now (Markus) > + perhaps auto-generate UI tests based on user-interaction. > + a few demo tests. > + UNO interactions is a great source of examples for UNO / Python > + checkout the uitest/libreoffice/ directory > + do the tests run headlessly ? (Caolan) > + yes; but they wait until a dialog is opened. > + added events to the LibreOffice code > + we wait for events eg. "this dialog is opened" > + are there any timeouts ? (Caolan) > + wait for 30 secs for a dialog to open - or it fails. > + are there plans to have this inside 'make check' ? (Miklos) > + wait - to see its proven to be stable. > + currently a pyuno bug with an assert in dbgutil builds > + until that's fixed, can't be added to make check; but plan to. > + tests are much slower than normal tests. > + if you have a choice between a UI test, or a normal test - use a normal > test > + start a dialog - ~1 second. > + add to 'make stagingcheck' ? (Bjoern) > + will add it there (Markus) > > * gtk3 libreoffice specific style classes (Bjoern) > + quite a lot of existing themes so far have a lot of glitches with gtk3 > compared to gtk2 > + have patched ubuntu theme bits around. > + pragmatic solution: add libreoffice-specific style classes. objections ? > + see e.g. https://github.com/horst3180/arc-theme/issues/659 > + gtk 3.22 - a stable release (Caolan) > + so theming fixes for earlier versions may be hopeless. > + "the next one will be the long term stable one" > + think its best to add style colours etc. (Michael) > + discussed with Benjamin some long time ago. > + dark themes are particularly problematic (Bjoern) > + similar bug on Qt4 - Breeze has b/g bits. > + its a feature not to have hard-coded colors - they fade & move etc. > + for widgetry - tabs / standalone bits no problem (Caolan) > + wrong colors for things with no match in gtk - totally right. > + while we use our own widgets: will always have problems. > + workaround in standardizing theme colors - acceptable. > + hopefully in future - use bigger gtk+ widgets etc. > + interested to know wrt. tabs being the wrong colors (Caolan) > + light text on a white background (Bjoern) > + dark theme uses dark primary toolbars & dark tabs. > + currently vendor patched in 5.2 (Bjoern) > + people patching their themes to use the vendor patch. > + now they want it in Debian > => standardize a mapping of our appearance colors and style > pieces / meta-data to gtk theme properties for 5.3 (Bjoern/Caolan) > > * Hackfests (Bjoern) > + next venues / suggestions > + FOSDEM - confirmed dev-room (Michael) > + preference for before FOSDEM (Eike) > + before - everyone just writes slides (Norbert) > AI: + book a couple of days beforehand at beta-co-working (Sophie) > + do we have a topic ? (Heiko) > + probably not. > + Girls-only event in Berlin, 29th October (Bubli) > + "Ladies who FOSS" (https://wikimedia.de/wiki/Ladies_that_FOSS) > + Bubli will be there, and so is Heiko > + now included into the list of projects: > https://wikimedia.de/wiki/Ladies_that_FOSS/Projects > + built a list of non-code easy-hacks; eg. palette issue. > + 33c3 CfP open: > https://events.ccc.de/2016/09/01/call-for-participation-33rd-chaos-communication-congress-en/ > (Bjoern) > + FSFE will be there, we can meet up with them. > + opportunity to do workshops there > + poke Bjoern if you want to show up. > + Hackfest Madrid, december with Gnome (Xisco/janI) > + Waiting for response from Gnome > + Hackfest Granada (Xisco/janI) > + in the early idea phase, but to be in Autumn > > * Updating ESC stats / bug pieces (Bjoern) > + no concern wrt. dropping writer:total > + if we break bits in core - should be quick at fixing it > + wanted non-filter, non-perf. issues in a separate counter. > + the smaller categories, and fewer bugs the better (Caolan) > + smaller groups find owners, interested in driving to zero. > + happened in the formula category > + driven those down from 8 - 2 thanks to Takeshi Abe > + referencing people who own regressions helps (Miklos) > + searching on comments makes this hard to un-mark yourself. > + some of these are old & gnarly, come from eg. re-base (Michael) > + closed lots of duplicates in regressions (Xisco) > + where the bisected commit was the same. > > * Mentoring / easyhack update (janI) > + < missing JanI > + > + Numbers are not available this week, as we are doing the final testing of > an updated script, > that is also used by QA > + will be back next week. > > * Commit Access > > * Developer Certification (Stephan/Bjoern/Kendy/Thorsten) > + no progress since last week ... some three possible names, hunting some > more. > > * Jenkins / CI update (Norbert) > from:Thu Sep 29 16:24:52 2016 > master linux rel jobs: 155 ok: 150 ko: 5 fail ratio: 3.23 % break: 4 > broken duration: 0.76% > master linux dbg jobs: 136 ok: 130 ko: 6 fail ratio: 4.41 % break: 6 > broken duration: 3.67% > master mac rel jobs: 109 ok: 105 ko: 3 fail ratio: 2.75 % break: 3 > broken duration: 0.45% > master mac dbg jobs: 117 ok: 113 ko: 3 fail ratio: 2.56 % break: 3 > broken duration: 3.08% > master win rel jobs: 118 ok: 116 ko: 2 fail ratio: 1.69 % break: 2 > broken duration: 0.37% > master win dbg jobs: 121 ok: 119 ko: 2 fail ratio: 1.65 % break: 2 > broken duration: 0.49% > master win64 dbg jobs: 115 ok: 114 ko: 1 fail ratio: 0.87 % break: 1 > broken duration: 0.13% > lo-5.2 mac jobs: 8 ok: 6 ko: 2 fail ratio: 25.00 % break: 1 > broken duration:13.38% > lo-5.1 mac jobs: 7 ok: 7 ko: 0 fail ratio: 0.00 % break: 0 > broken duration: 0.00% > branch gerrit all jobs: 24 ok: 21 ko: 3 fail ratio:12.50% > master gerrit lin jobs: 176 ok: 155 ko: 21 fail ratio:11.93% > master gerrit plg jobs: 175 ok: 120 ko: 55 fail ratio:31.43% > master gerrit win jobs: 175 ok: 120 ko: 54 fail ratio:30.86% > master gerrit mac jobs: 175 ok: 154 ko: 21 fail ratio:12.00% > master gerrit all jobs: 175 ok: 90 ko: 84 fail ratio:48.00% > + a normal weeks' numbers - back to where they're supposed to be. > > * l10n (Sophie) > + Indian team working on improved Indic participation > + building an action plan to discuss tomorrow. > > * QA update (Xisco) > + Bug Hunting Session? Anyone championing that? (Bjoern) > > + Matthew Francis shared max4.1 and max4.2 > + found repos for bibisection, one build per commit > + so we can get down to the individual commit. > > + adding deltas to last week: > + UNCONFIRMED: 702 (-35) > + enhancements: 60 (-8) > + needsUXEval: 10 (-15) > + haveBackTrace: 19 (-1) > + needsDevEval at 427 (-92) > + needsDevAdvice at 39 (+7) > > + Most Pressing Bugs: http://tdf.io/mostressingbugs > + moststressing bugs - zero open > + this is severity changed to critical in last eight days. > + useful to bring them here - so QA people reading the minutes can > look ... > + not so useful to discuss if don't have full details (Michael) > + tdf#98365 - Crash on first run of 64-bit build with no user profile > + NEEDINFO. > + tdf#94225 - Writer crashes on undo > + needs bisection & a good trace. > + tdf#101528 - Crashes on 3D chart modification > + needs a good debug symbols trace and/or bibisceting > + tdf#101726 - crash when selecting column and pressing ⌘1 or clicking > menubar Format > Cells > + macOS - SfxItemSet assertion fires. > > + Mail merge regressions: http://tdf.io/mmregressions > + 2 open; 2 open last meeting > > * QA stats > > + https://bugs.documentfoundation.org/page.cgi?id=weekly-bug-summary.html > +152 -176 (-24 overall) > many thanks to the top bug squashers: > Buovjaga 35 > Xisco Faulí 24 > Caolán McNamara 20 > Markus Mohrhard 7 > V Stuart Foote 7 > Jean-Baptiste Faure 5 > m.a.riosv 5 > Michael Meeks 5 > Yousuf Philips (jay) 4 > Adolfo Jayme 4 > Jan-Marek Glogowski 4 > Heiko Tietze 4 > Andras Timar 4 > Gabor Kelemen 3 > Cor Nouws 3 > > * Highest-Priority bugs (aka "MABs"): > 5.2: 1/17 - 5% > 5.1: 3/31 - 9% > 5.0: 6/56 - 10% > 4.4: 7/74 - 9% > 4.3: 4/69 - 5% > 4.2: 7/133 - 5% > 4.1: 4/79 - 5% > 4.0: 7/82 - 8% > old: 30/246 - 12% > > + http://bit.ly/2dp3mwC > > * Bibisected bugs open: keyword 'bibisected' > + 337/1477 349/1463 349/1445 347/1431 338/1407 325/1390 325/1383 325/1383 > + http://bit.ly/2cSCXlS > > * all bugs tagged with 'regression' > + 647(-35) bugs open of 5176(+33) total 7(-3) high prio. > > * ~Component count net * high severity regressions > Calc - 4 (+0) > LibreOffice - 1 (+0) > Impress - 1 (+0) > Base - 1 (+0) > Writer - 0 (-3) [ Amazing ! ] > + http://bit.ly/1HWHb3E > > * ~Component count net * all regressions > Writer: other - 119 (-4) > Calc - 118 (-6) > Impress - 50 (-2) > Writer: docx - 44 (-4) > graphics stack - 42 (-1) > UI - 37 (-3) > LibreOffice - 36 (-3) > Borders - 30 (-1) > Base - 29 (+0) > Draw - 28 (+0) > Writer: doc - 27 (-1) > Crashes - 24 (+0) > filter / storage - 16 (+0) > print / PDF export - 14 (+1) > Chart - 13 (-1) > Writer: perf - 11 (-2) > BASIC - 10 (-1) > Writer: filter - 5 (+0) > Extensions - 3 (+0) > Formula Editor - 2 (+0) > framework - 2 (+0) > sdk - 1 (+0) > Linguistic - 0 (-1) > + http://bit.ly/1BUdI8i > _______________________________________________ > LibreOffice mailing list > libreoff...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/libreoffice _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreofficeemail@example.com Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/