Re: [Libreoffice-qa] QA Meeting Minutes (2017-04-25)
Hi folks, On Thu, Apr 27, 2017 at 05:13:43PM +0200, Xisco Fauli wrote: > Hello, > > > * QA telegram group (x1sc0, 16:17:48) > > * buovjaga> yeah forums are better for asynch discussion (x1sc0, > > 16:23:03) > > * cloph is sceptical, doesn't think telegram would be > > newcomer-friendly (not as widespread like e.g. twitter/facebook), > > and also cannot see what kind of conversations it would be good for > > (cloph, 16:38:43) > > * LINK: > > https://m.signalvnoise.com/is-group-chat-making-you-sweat-744659addf7d > > (buovjaga, 16:41:56) > > Group created: https://t.me/LibreOffice_QA I havent been in the call, but I have no right to object here. ;) Allow me to add a very specific request on this though: - please try to define really well and clean cut, what the best/prefered communication channel for a specific topic is - please also define well an clean cut, which topic are tolerated on other channels and why The thing to avoid is having a topic dicussed on multiple channels, which might lead to different sub-groups of the community to reach different (and conflicting) consensus on topics on different channels. Prior examples of such borders are: - RedMine vs. Bugzilla "everything about the product LibreOffice belongs on bugzilla, no exceptions" - AskBot vs. Bugzilla Inexperienced users might start on AskBot to triage their issue (which might a support question, not a bug), but once a bug is well-triaged it must move to bugzilla. - #libreoffice-dev vs. user support on IRC see /topic: "This is the LibreOffice DEVELOPER channel. For user questions & problems without code go to #libreoffice ..." Once you have a clean cut definition on what can be discussed on telegram (and when the discussion should be moved to bugzilla or whereever ...), it should be noted in the channel description (and probably also on the TDF wiki listing all comms and the mapping of topics). E.g. the "single source of Truth" on LibreOffice bugs is always Bugzilla. You can chat about bugs elsewhere, but as long as its not reflected on Bugzilla, others in the community are not required to know about it and in case of doubt, its your duty to copy relevant info over to Bugzilla[1]. (This is nothing new either, e.g. it happens that devs copy over IRC conversations over to Bugzilla.) And with that Im finished proselytizing. ;) Best, Bjoern [1] And corollary: "But we had a different conclusion about that bug on telegram." by default is void against whatever is in Bugzilla, if the two are conflicting. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Fri, Jan 13, 2017 at 04:41:44PM +0100, Alexander Thurgood wrote: > So, dropping make 3.8.1 on Mac would clearly push people not to build > with the XCode system provided tools ? Well, it is still GNU make. But yes in general, its suggested to work on LibreOffice in a well defined environment anyway, which for OSX and Windows is LODE. Best, Bjoern (FWIW, GNU make 3.82 was released 2010-07-28: Its older than LibreOffice itself, and it is trivial to build with older versions of generic POSIX make including GNU make 3.81.) ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Dec 15, 2016 at 12:19:54PM +0100, Cor Nouws wrote: > Michael Meeks wrote on 08-12-16 17:56: > > + Mail merge regressions: http://tdf.io/mmregressions > > + 4 open; 4 open last meeting (2 OSX, 1 Linux, 1 generic but hard > > repro) > > => drop from the QA section from now - always four. > > Counting 5 at the moment. Yes, but the rationale was the extraordinary number of MM regressions we had during the cleanup of the old (really horrible) code. That major cleanup is finishe for the most part now, activity in the area is back to normal, so no justification anymore to highlight MM regressions over regressions elsewhere. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Dec 08, 2016 at 04:56:07PM +, Michael Meeks wrote: > + someone creating e.g. a Visual Studio extension that does > all the cygwin/git clone/gerrit bootstrapping would be much appreciated > though (Bjoern) > [...] > + eg. a pre-canned bundle with pre-built 'externals' and > pre-canned VS file made from make (Michael) ... and the core issue with that is the number of different configs we support even on Windows. While that makes some sense on Linux, where each distro is a unique snowflake in some way, it makes very little sense on Windows, where most things should be the same on all systems. Or at least _could_ be the same on all systems. I mean, we could have a tinderbox run "./autogen.sh && make vs2013-ide-integration" once a week and make it commit the result Visual Studio solutions to the core repo. Note this does _not_ need a full build anymore, so should be a matter of minutes. But for those to work universally, it requires tooling that reproduces pretty much exactly as on the canonical tinderbox that created the solutions, including: - SRCDIR - BUILDDIR - cygwin install LODE did some great steps in that direction, but I fear is not quite there yet. If you get Windows builds to kill all those degrees of freedom, then this should work just fine (including pre-build 'external'). So again: This is less of an build issue, than one of configuration management. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] 41max and 42max bibisect repositories?
Hi, On Tue, Oct 04, 2016 at 04:08:03PM +0200, Xisco Fauli wrote: > I'm afraid that's not right. Indeed, the 43all contains the old 43only/42only/41only etc. -- not the XXmax ones. Just looking at the history in the wiki, the download links to TDF servers still seem to work though: https://wiki.documentfoundation.org/index.php?title=QA/Bibisect/Linux=117634 Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] 41max and 42max bibisect repositories?
Hi, On Tue, Oct 04, 2016 at 01:23:05PM +0200, Xisco Fauli wrote: > Does anybody know anything about 41max and 42max bibisect repositories > mentioned in this video: > https://www.youtube.com/watch?v=WLmEfvjVN7s=07m39s ? > I can't find them anywhere but it would be wonderful to have those too. They have been removed on the rationale that someone looking for an bug as old as between 4.0 and 4.1 or 4.1 and 4.2 is rather rare and if it happens -- they should just download the 43all repo. FWIW, 43all contains the builds from 41max and 42max (and then some) -- so when server admins complained about use of disc space, the latter where deleted as the former can do everything they can. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call: 2016-08-18
Hi, On Thu, Aug 18, 2016 at 06:36:50PM +0200, Bjoern Michaelsen wrote: > AI: + bring patch for Writer regression stat update (Bjoern) Done: https://gerrit.libreoffice.org/28239 Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
[Libreoffice-qa] UX bugzilla queries (was: minutes of ESC call: 2016-08-18)
Hi Heiko, On Thu, Aug 18, 2016 at 06:36:50PM +0200, Bjoern Michaelsen wrote: > * UX Update (Heiko) > + from: > http://nabble.documentfoundation.org/kendy-collabora-com-Minutes-of-ESC-call-2016-08-11-tp4190974p4190988.html > + ux-advice: keep it, because many bugs are not easy to file against > a certain component > + tracking of needsux: sure, can do that; but many people may > understand enhancements similar to ux, which needs to get covered (or better > we restrict our trust in the numbers) > + no semantic difference between "component:LibreOffice > keyword:needsUXeval" and "component:ux-advise" (Bjoern) > + introduced keyword, to allow component linked (Heiko) > + component for newcomers (Heiko) > + personally like to keep both (Heiko) > + 350 and 150 in each bucket (Bjoern) > + component:LibreOffice is the catch-all (Bjoern) > + watch compoment for mailing list? (Heiko) > + get a email for every bug change and filter (Thorsten) > + ML create false impression there might be a discussion (Thorsten) > + actual discussion should happen (Eike) > + RSS Feed for query: > https://www.bugzilla.org/features/#buglist-formats (Jan-Marek) > AI + move component:ux-advise to component:LibreOffice keyword:UX as > ninja-edit (Robinson) > + get checkbox for bugzilla (Heiko) > + we have 500 ux bugs, we dont need to make it much easier right now > (Bjoern) here is a query wrt. UX on bugzilla to get you started: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMED_status=NEW_status=ASSIGNED_status=REOPENED_status=RESOLVED_status=VERIFIED_status=CLOSED_status=NEEDINFO_status=PLEASETEST=-7d=Now=needsUXEval%2C%20_type=allwords_id=628531=LibreOffice_format=advanced=--- (unresolved bugs with keyword:needsUXeval touched in the last 7 days) you can modify and tweak this with the "edit search" button. Also note the XML, CSV, RSS buttons which can be used in a skript. This: https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/scripts has a few examples of libreoffice scripts using bugzilla. As Thorsten noted, using: https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs as an event stream and filtering that should also work. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
[Libreoffice-qa] minutes of ESC call: 2016-08-18
* Present: Norbert, Sophie, Armin, Stephan, Robinson, Christian, Thorsten, Jan-Marek, Bjoern, Eike, Miklos, Lionel, Olivier, Heiko * Completed Action Items: + fixed with 62c4a8aacf76771e97a8da35096e6ad69a11979a - was: explain the reason why "make debug=T" doesnt build with symbols anymore / bring it to some ESC when Stephan is here (Stephan / Bjoern) + for breeze etc. originals, find out who needs commit access & enable them to do it (Heiko) + Breeze & co. originals in git should be done http://nabble.documentfoundation.org/kendy-collabora-com-Minutes-of-ESC-call-2016-08-11-tp4190974p4190988.html + approve https://gerrit.libreoffice.org/#/c/27028/ and https://gerrit.libreoffice.org/#/c/27857/ (Cloph) * Pending Action Items: + poke at MSDN licenses (Michael) [ waiting for a response on new process, on holiday ? ] + investigate a cron job that queries & auto-merges (Norbert) [ the solution proposed by David - using his query & a JSON script to refine it - will work - needs a bit more python (Norbert) ] + tweak UI and get LiveConnect API key / build case for board (Christian) + still need to get API key, rest is done + attempt to re-build a recent gstreamer 1.0 / core spec file on our CentOS6 base (tdf#94508) (Christian) + Program committee to work on the Conf. program (Kendy, Thorsten, Italo, Marina) * Release Engineering update (Christian) + no release this week, rc1 last week rc2 next week (cloph) + all on track (cloph) + 5.1 → 5.1.6 rc1 Oct 4th + 5.2 → 5.2.1 rc2 next Tue (Aug 23rd) + 5.3 → 5.3.0 alpha 1 Oct 18th + Android & iOS Remote * LibreOffice Conference in Brno (Kendy) + kendy away, anyone else? + shm_get: see ya there + erAck: prep slides! * Membership Committee plug (Michael) + Please send nominations and self-nominations via e-mail to electi...@documentfoundation.org (which reaches the Board of Directors in private) and also (!) to board-disc...@documentfoundation.org (which is a public mailing list). We kindly ask nominees who would like to stand for elections to provide a statement of up to 75 words on their candidacy as continuous text (so no bullet lists or multiple paragraphs). In addition, please also provide your full name, e-mail address and your corporate affiliation, if any, and please announce that you will provide information on all future changes as soon as possible. + tooling uses git & is user-friendly for devs. * Documentation (Olivier) + Help page for doc classification in. -> vm173.documentfoundation.org/text/swriter/classificationbar.xhp + Preparing help page for CMIS setup and usage -> Found CMIS access very slow in cmis.alfresco.com/cmisatom -> will install Alfresco community in laptop to study check-in/check-out real case + Writer Guide book under review by Jean Weber + Getting Started 5.2 open for update -> Community slow to jump in (vacations?). + Bjoern: blocking on something from dev/infra? + infra to put link for Q for 5.3, not urgent (askbot or something else) * GSoC 2016 (Thorsten) + Next deadline is August 23rd 19:00 UTC for students to submit their work + Mentors then review, final deadline for mentor eval is August 29th + reminder - blogging at a minimum helps docs / QA teams etc. + !!! soft pen-down next Monday (15th), on 23rd deliver & package + to be frozen and delivered after that + important that the students deliver that on time, otherwise they'll be failed + 6 students attending the Conference + no news, make students document/blog wildly (Thorsten) * UX Update (Heiko) + from: http://nabble.documentfoundation.org/kendy-collabora-com-Minutes-of-ESC-call-2016-08-11-tp4190974p4190988.html + ux-advice: keep it, because many bugs are not easy to file against a certain component + tracking of needsux: sure, can do that; but many people may understand enhancements similar to ux, which needs to get covered (or better we restrict our trust in the numbers) + no semantic difference between "component:LibreOffice keyword:needsUXeval" and "component:ux-advise" (Bjoern) + introduced keyword, to allow component linked (Heiko) + component for newcomers (Heiko) + personally like to keep both (Heiko) + 350 and 150 in each bucket (Bjoern) + component:LibreOffice is the catch-all (Bjoern) + watch compoment for mailing list? (Heiko) + get a email for every bug change and filter (Thorsten) + ML create false impression there might be a discussion (Thorsten) + actual discussion should happen (Eike) + RSS Feed for query: https://www.bugzilla.org/features/#buglist-formats (Jan-Marek) AI + move component:ux-advise to component:LibreOffice keyword:UX as ninja-edit
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Jun 02, 2016 at 06:46:39PM +0200, jan iversen wrote: > - To extend my nightly statistic script, to check new commits (probably > restricted to our code repo). > - For every commit If the delta between the last commit from the author and > this commit is more than 1Year, the script will notify me. > - I will write a "happy to see you again" mail, with copy the dev list, so > the author hopefully starts to be an active part of the community again. Sounds great! For the last point, it might make sense to have a look at that first-after-a-year commit for two reasons: - to (mildly) personalize the "happy to see you" mail - to superficially check for something fishy being sneaked it via a stolen key and ID Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Apr 07, 2016 at 03:36:07PM +0100, Michael Meeks wrote: > + Made some progress on writer regressions (Bjoern) > + could close some - have commits, but not closed. + count is at 6 currently (all severity minor): + 2 SimpleWinLayout still (was reverted already?) + 2 more with committed fixes + 1 more Windows only + 1 general + http://nabble.documentfoundation.org/Getting-LibreOffice-Writer-5-0-6-bibisected-regression-free-against-LibreOffice-4-4-0-was-LibreOffic-td4179580.html#a4179743 Assuming 2 SimpleWinLayout bugs can be closed as can those with committed fixes, we are left with only 2 bibisected writer regressions (1 on non-windows) left open from LibreOffice 5.0.0. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
[Libreoffice-qa] Getting LibreOffice Writer 5.0.6 bibisected regression free against LibreOffice 4.4.0 (was: LibreOffice ESC call, ...)
Hi, On Wed, Mar 23, 2016 at 10:19:58PM +, Michael Meeks wrote: > * QA stats > * Bibisected bugs open: whiteboard 'bibisected' > + 399/1305 404/1297 406/1292 412/1284 408/1277 403/1260 398/1248 > + http://tdf.io/bibibugs > > * all bugs tagged with 'regression' > + 773(-12) bugs open of 4798(+10) total 28(-2) high prio. > > * ~Component count net * high severity regressions > Calc - 11 (-2) > Writer - 9 (+0) >LibreOffice - 4 (-1) > Base - 2 (+0) > Extensions - 1 (+1) >Impress - 1 (+0) > + http://bit.ly/1HWHb3E > > * ~Component count net * all regressions > Writer - 242 (-1) > Calc - 166 (-7) >LibreOffice - 56 (-3) >Crashes - 51 (-3) >Impress - 46 (+0) > UI - 41 (-1) > graphics stack - 36 (+1) > Base - 34 (+0) >Borders - 32 (+0) > Draw - 26 (-1) >filters and storage - 22 (+0) > Chart - 14 (+0) > BASIC - 14 (+1) > Printing and PDF export- 10 (-1) > Formula Editor - 7 (+0) > Linguistic - 4 (+0) > Extensions - 3 (+0) > Installation - 2 (+0) >sdk - 1 (+0) > framework - 1 (+0) > + http://bit.ly/1BUdI8i So, we have a few more week until we close the 5.0 series with the 5.0.6 release. I would think it would be awesome for us to aim for closing all triaged, confirmed and bibisected regressions that were introduced betweem LibreOffice 4.4 and 5.0 by then. As writer has the highest absolute regression counts, I would suggest to start with that goal there for closing the 5.0 series. Looking at: https://bugs.documentfoundation.org/report.cgi?x_axis_field=component_axis_field=bug_severity_axis_field=_redirect=1_format=report-table_desc_type=allwordssubstr_desc==LibreOffice_status=NEW=---_type=allwordssubstr=_file_loc_type=allwordssubstr_file_loc=_whiteboard_type=allwordssubstr_whiteboard=_type=allwords=bibisected%2C+_id=_id_type=anyexact=substring==substring==substringNow_top=AND=version=regexp=^5.0=table=wrap LibreOffice Writer has only 8 unresolved, fully confirmed, triaged and bibisected regressions today. So getting LibreOffice Writer "bibisected regression clean" for 5.0 should be doable. By priority IMHO the remaining unresolved issues are: - tdf#94063: critial, all platforms - tdf#94570, tdf#94449, tdf#97103: non-critical, all platforms - tdf#95836, tdf#94597, tdf#95194: all caused by same commit, Windows only - tdf#96716: Windows only I love TDF to be able to claim that LibreOffice Writer 5.0.6 has no bibisected regression against LibreOffice Writer 4.4.0. Its a good story for users, it shows that we got better by a long way from our earlier releases and -- its also motivating for those doing tireless work on QA and bibisecting. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] Beginners guide to QA
Hi, On Mon, Mar 07, 2016 at 04:39:49PM +0400, Yousuf 'Jay' Philips wrote: > I had suggested that a beginners guide to QA be created during one of the QA > meeting some time back and would appreciate people's feedback on what has > been written so far and what additions can be added, so that i can be > complete and added to the wiki. > > https://docs.google.com/document/d/1CGhkvqZBg-G_uYJFiNS8-d-P2VjyDE8Z2-rtqM__VG4/edit# Nitpick here, but: Is there any good reason not to do this on http://pad.documentfoundation.org/ or on a staging page on the wiki right away? Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Feb 25, 2016 at 04:52:28PM +, Michael Meeks wrote: > * Hackfests (Bjoern) > + next venues / suggestions > + Ankara, Turkey > + https://wiki.documentfoundation.org/Hackfest/Ankara2016 Confirmed date for the weekend now. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] Minutes of ESC call [2016-02-04]
Hi, On Thu, Feb 04, 2016 at 08:59:16PM +0100, Jan Holesovsky wrote: > * Hackfests (Bjoern) > + Turkey > + talked to them; lots of enthusiasm & desire for training. > + mid-March hack-fest expected. > + concrete dates ? > + concrete volunteer mentors? > + Jan-Marek maybe highlighting this item for visibility: We are contemplating a Hackfest in Turkey, but it would be good to have at least some experienced mentors to go there. If you are interested, please contact me on list or off list. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org 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/
Re: [Libreoffice-qa] Testing Windows builds on Linux with PlayOnLinux?now possible!
Hi, On Thu, Feb 04, 2016 at 08:05:39AM +, Pieter Kristensen wrote: > Great that it works so well on PlayOnLinux. But how about Wine? PlayOnLinux is an easy install wrapper for wine. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] Testing Windows builds on Linux with PlayOnLinux now possible!
Hi Gouchi, all, awesome news: Gouchi set up LibreOffice on PlayOnLinux (see https://www.playonlinux.com/)! This means you can now install LibreOffice Windows builds running in Wine with just a few clicks on Linux. Please try it out and provide feedback here or at: https://bugs.documentfoundation.org/show_bug.cgi?id=87743 This should help a lot with triaging regressions, verifying fixes and checking/confirming if bugs are playformspecific. I hope this is highly helpful for QA work. Using this should be straightforward, but if one of you wants to update docs in the TDF wiki or make a screencast about this, that might make things even better. Thanks a lot to Gouchi for the work on this! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] LibreOffice releases (was: Reminder: QA Meeting on Wednesday)
Hi, On Wed, Nov 25, 2015 at 04:27:58PM -0700, Pedro wrote: > But since you can't ask the developers to do such a boring job, even that > won't solve the problem... Thats not entirely true. Yes, just asking some random developer to fix some random regression (likely by another developer) is a very bad idea as it assumes guilt by association. Bibisecting a regression and asking the developer who causes the regression to fix it ... is less of a problem. There still might be valid reasons from this developer not being able to care for this particular regression at this point in time, so dont assume this to be a strictly mechanic thing. Note however that regressions _are_ being watched at the ESC. And people are also watching who caused them (which is only possible when they are bibisected) and where -- at least I am doing this already for quite a while. Im not calling names in public though, as that would likely be very counterproductive. It would only be a last resort if things go really out of hands. So QA can help here by really bibisecting bugs: Bibisected bugs tell developers where we cant be braver and we are going too fast and loose. Good data on bibisected regressions allows developer to handle things properly. However, organizing the response has to happen between the developers (e.g. on the ESC) as it would be foolish to assume a strictly mechanical handling to be helpful here. Best, Bjoern P.S.: If you want to raise visibility to regressions in a helpful way, I suggest you start with a _positive_ motivation for developers. E.g. QA giving out a badge each month for the three developers with (most simple approach): - a/ the most commits - b/ without a regression known to be bibisected down to a commit of him/her I assume something like that might create some good and _positive_ motivation in the right direction ... ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice releases (was: Reminder: QA Meeting on Wednesday)
Hi, On Wed, Nov 25, 2015 at 03:40:37AM -0700, Pedro wrote: > A sugestion: maybe have a branch dedicated to bug fixes every other year? > Example: let's say 5.1 is dedicated to fixes. Then a slight change of > schedule would postpone 5.2.0 to some months later so that most devs would > concentrate on 5.1 (of course new features would still be added to Master in > this period) instead of being split by two concurrent branches... We have a "branch dedicated to bug fixes" twice a year. They are called "release branches" and live for about a year each. More details at: https://www.youtube.com/watch?v=7DBzRfW8R5k http://conference.libreoffice.org/assets/Conference/Aarhus/Slides/BjoernMichaelsenreleases.pdf If you need a branch that is living longer than a year, that is possible too, but nothing volunteers would commit to. It is offered by various L3 supporters of LibreOffice though: http://www.documentfoundation.org/certification/developers/ Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] LibreOffice releases (was: Reminder: QA Meeting on Wednesday)
Hi, On Wed, Nov 25, 2015 at 10:10:58AM -0700, Pedro wrote: > Maybe my suggestion wasn't clear. I know about the "twice a year" release > branches. My suggestion was exactly to delay the second release of the year > so that developers could have more time to dedicate to a single branch (of > course they could always submit new features to the Master branch) That wouldnt help at all, "delaying the release" is just another name for "not making an release from master for a longer period of time" and thus would result in _more_ regressions, not less. LibreOffice is already doing exceptionally long release cycles compared to the rest of the open source software world. All of this is being discussed in the linked video, I suggest you watch it. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Nov 12, 2015 at 04:37:28PM +, Michael Meeks wrote: > * Hackfests (Bjoern) > + GNOME hack-fest in Madrid - Dec 2nd -> 4th (Jacobo) > + sent an invitation to LibreOffice deployments in Spain > + they may need funding to attend. > + Wiki page pending - Bjoern working on it. Inital setup here: https://wiki.documentfoundation.org/Hackfest/Madrid2015 please be a good wiki citizen and add/modify/correct at your hearts pleasure! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Bugzilla: Adding new Status for 'abandoned' bugs?
On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote: > Insufficient Data though can also be used for situations where a bug can > not be reproduced due to, well, insufficient data.. i.e. happened one > time crash and no stack trace, no exact steps to reproduce, even if the > reporter was or would be willing to provide ... all cases where > WORKSFORME sounds a bit odd and lax (which is a valid resolution if the > given steps do not lead to the described failure), but ABANDONED > wouldn't fit either, IMHO.. That would almost NEEDINFO. The only difference between NEEDINFO and INSUFFICIENT DATA is that one is considered resolved, while the other one isnt and there is no way to see from the wording that NEEDINFO is the unresolved one and INSUFFICIENT DATA is the resolved one. Its likely that will lead to confusion. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi Xisco, On Fri, Oct 30, 2015 at 09:55:57AM +0100, Xisco Faulí wrote: > > * Hackfests (Bjoern) > > + Could we join the GNOME hack-fest in Madrid ? (Bjoern) > I'm currently living in Madrid and I'd like to attempt the meeting. It goes > without saying that I can give a hand on the field if help is needed. You are most welcome! Looking forward to meet you there. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [libreoffice-design] Re: Minutes of the Design Hangout: 2015-10-07
On Fri, Oct 30, 2015 at 07:21:22PM +0400, Yousuf 'Jay' Philips wrote: > Not sure how well breeze with the ubuntu theme and it maybe better to use > tango. I have the seal of approval from the Canonical Design Team -- not gonna do extra rounds beyond that now. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of the Design Hangout: 2015-10-07
Hi, On Fri, Oct 09, 2015 at 10:13:43PM +0200, Jan Holesovsky wrote: > * 'industrial' icon theme - keep or remove? > > + https://gerrit.libreoffice.org/#/c/19149/ > + Human also depends on Industrial (Jay) > + should that be actually depend on Tango? (Jay) > + best to talk to Bjoern (Michaelsen) (Kendy) Human has already been broken by tdf#93145 in LibreOffice 5.0. There is no way Ubuntu will ship a huge set of fallback themes to make Human complete again, thus we only ship themes with galaxy as fallback -- the ultimate fallback. For upcoming releases see lp#1506544: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1506544 Note that does NOT mean we should immediately drop human. At least for 5.1/xenial it should be kept an transitional option. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of the Design Hangout: 2015-10-21
On Wed, Oct 28, 2015 at 06:54:47PM +0100, Jan Holesovsky wrote: > * Present: Heiko, Jay, Kendy, Tomaz, Stuart > > * UI changes integrated the last week: > > + Enable auto-numbering by default reverted for now (Samuel) > + First/last button in the Calc tab bar (Tomaž) > + NotebookBar proof-of-concept pushed (Kendy) > + alt-x support to math (Justin) > + more 32px Breeze icons (Andreas) > + Appearance -> Application Colors (Adolfo) > + initial "Home" NotebookBar tab proof-of-concept (Samuel) > + make sidebar toolboxs item order RTL sensitive (Bubli) + proper scrollwheel handling in TabBar/Sidebar (Bjoern) ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] When it's time to basic bases?
Hi Miguel, Hi Joel, On Sat, Aug 01, 2015 at 08:30:19AM -0700, Joel Madero wrote: I skimmed this and really...this isn't how the team works. We don't have someone come and insist and dictate how we do our work. If you want then the best thing for you to do is lead by example and then if it works, others will follow. With that, I'm not going to say anything specific with regards to anything in this because it's just a lot of insist on a massive amount of changes and telling volunteers how to do their volunteering. Really not how the project works. I agree with Joel here, but like to provide one addition: Aiming to communicate about changes earlier is of course still a worthwhile goal. If you want to improve the situation here e.g. by watching the commit stream, asking commiters for more details about their changes etc. -- that would be a most valuable contribution, if those results are then published in a more accessable form (on a blog for example). For starters it might make sense to focus on one specific application for that (say: Calc or Writer). Unlike asking others to contribute differently, such work would indeed likely be much appreciated by all parties involved. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2015-07-30
Hi, On Sun, Aug 02, 2015 at 06:25:05PM +0200, Markus Mohrhard wrote: That is already possible with cppunit. Instead of using CPPUNIT_TEST use CPPUNIT_TEST_FAIL which tells cppunit that the test is expected to fail with a cppunit exception being thrown (it is extensively used in the cppunit internal unit tests). The test will start to fail when none of the asserts fail anymore. Keep in mind that it might be dangerous to use this with more than one assertion as an unexpected one might fail. Additionally there is CPPUNIT_TEST_EXCEPTION which expects as second parameter the expected exception. So this is a replacement for the following pattern that can sometimes be found in our code: Yes, but for one we do not only have c++ tests, esp. since one of the aims is to get bugreporters (aka a broad audience) to improve their reports by adding (failing) tests: + writing a test needs some knowledge, couldn't we actually mentor the author to do a fix too? (Kendy) + can be much harder (Norbert, Bjoern) Also there might be unstable tests, for which expecting reliable failure is not what we want (rather we want to ignore unstable tests until they are stable and non-failing). Thus: + 'make -k stagingcheck' - for tests that do not have a fix yet (Bjoern) That doesnt preclude using the cppunit features you describe for really expected failures/exceptions, so thanks for the hints! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] daily MAB summary and CCing of MABs (was: MAB/Priority and Severity)
On Mon, Jun 29, 2015 at 11:57:10AM +0200, Eike Rathke wrote: What exactly do you mean with review here? I don't think we should spend too much time on that during the ESC call, but I'd be ok with some does anyone see a bug on this list that shouldn't belong there topic. Yes, the latter is actually pretty much what I had in mind for the ESC 'review'. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] MAB/Priority and Severity
Hi, On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote: So the time has finally arrived that we are moving forward with _locking out priority/severity_. This means that *MAB will be retired*. I'd like to suggest to add this query as a reocurring item for the Robinson and the rest of the call to look at during the QA section of the ESC call: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDbug_status=NEEDINFObug_status=PLEASETESTchfield=prioritychfieldfrom=-8dchfieldto=Nowchfieldvalue=highestlist_id=545001priority=highestproduct=LibreOfficequery_format=advancedresolution=--- It shows: - open bugs - that were changed to priority highest (thus a MAB) in the last 8 days (aka ~since the last call) - and currently are still priority highest (and thus a MAB) This is for the ESC to both be aware of newly marked important bugs -- and also to weed out one or another wrongly marked high priority bug. Also, this should help us keep the total number of high priority bugs both under control and on the radar. @Robinson: Can you take that up? Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Jun 18, 2015 at 06:04:04PM +0100, Michael Meeks wrote: + request more KDE testers ... (Bubli) + KDE in rather a sorry state - a month to reproduce a bug. + none of the tinderboxes build with KDE vclplug support. + F19 tinderbox can build with that (Thorsten) + B3 release for Ubuntu has KDE packages (Bjoern) + not installed by default; in a PPA + if using Kubuntu will get that pkg AI: + for bug hunting - point at PPA (Robinson) The ppa in question is: https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases and currently has rough 5.0.0~beta3 packages including kde support for Ubuntu 15.10 (vivid), Ubuntu 14.04 LTS (trusty) and Ubuntu 12.04 LTS (precise). Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] TDF Grant Request/Proposal: LibreOffice project dashboard/All about LibreOffice
Hi all, Hi TDF treasurers, The Document Foundation has a grant request page for some time now: http://www.documentfoundation.org/grant-request/ to allow members of the Docuemnt Foundation to actively make suggestions on projects and efforts that should be funded to bring LibreOffice forward. The Board of the Document Foundation did of course collect and approve projects for LibreOffice before, but going ahead we will try to make public as much proposals for funding as possible even before approval for transparency. One of the older preexisting proposals still under consideration is a Dashboard for the LibreOffice project that shows what is going on in all parts of the project. I have tried to fill this proposal with life by bringing it in the form expected by the grant-proposals page. See below for the full text of the proposal. Along with this mail, I have send this grant request to treasu...@documentfoundation.org as suggested on the grant-request webpage. If you are member of TDF supporting this project, think it should be funded and most importantly want to help out in either overseeing the tender or otherwise getting it executed, please make yourself heard: Your help will be appreciated. Note as of now, this is just a _proposal_ and a draft: It hasnt been approved by the Board to receive any funding yet. However, given the vast amount of regular data going towards LibreOffice contributors (in development alone: tinderbox status, gerrit submissions, cppcheck updates, coverity updates, lcov updates to name a few) personally I think this is getting more important every day. The Board of the Document Foundation will have to weight its impact against a lot of other proposals -- many of them excellent -- in the next 'budgeting round'. Best, Bjoern Grant request/proposal follows below: == grant details == Grant Proposal: Creating a LibreOffice community and developer dashboard (All about LibreOffice) a cost estimate has been shared with the Board of the Document Foundation ini private for budget approval and reservation of funds Grant objective: Create a webpage showing latest activity, summaries and trends of the LibreOffice project in all areas: development, qa, user-to-user support etc. The webpage should be easily extensible for developers providing scripts analysing current and historic data from various project infrastructure. Grant size: to be tendered Grant beneficiaries: tender contractor Grant follow-up: Frameworks, languages and tools used should be popular and widely used to allow the result to be community maintained and sustained after initial development. Extensibility should allow developers to refine the dashboard without deep insight in the used frameworks and tools. Blog posts should advertize the dashboard to the LibreOffice community and invite contributions. === User stories === As a LibreOffice community member, I want to be able to find out about the latest events and actions happening in the project today presented on a webpage. Updates do not need to be real-time, but delays should not be bigger than 1-2 hours. As a LibreOffice community member, I want to be able to find out about the latest events and actions happening in the project since my last visit presented as a newsfeed (RSS/Atom) for my reader. As a LibreOffice community member, I want to be able to create a newsfeed that filters for interest of specific interest for me. As a LibreOffice community member, I want to be able to query filtered on if an event creates or resolves an action item for a specific subproject. Here are some examples based on Bugzilla: regression filed would be qa-task-created (need confirmation/triage), regression triaged/moved to NEW (qa-task-resolved, dev-task-created), regression fixed (dev-task-resolved). As a designer, I want to be able to improve layout and looks of the dashboard with just basic knowledge on coding. As a designer, I want to be able to create subpages that present filtered information of interest to a specific subproject e.g. events and actions of interest for development, of interest for QA etc. As a programmer, I want to be able to feed events and actions happening on any system of the project to be displayed to the system simply by adding a script generating a RSS/Atom newsfeed to an existing repository using only existing credentials (gerrit account). At least all common *nix script languages (Python, Perl, Ruby, PHO) should be supported, even C/C++/Haskell/Ocaml should be possible unless there are overwhelming troubles. As a programmer, I want to be able supply summaries and aggregate data by querying for existing events in the system and simply parsing a RSS/Atom newsfeed. I want to be able to send these summaries as an event just like others. As a programmer, I want to associate events send to the system with tags because that allows to query for specific types of events either for summaries or for presentation on subproject pages. As a
[Libreoffice-qa] Fixed and included new lcov numbers: Regression hotspots updated
Hi, On Fri, Jun 12, 2015 at 01:41:15AM +0200, Bjoern Michaelsen wrote: == Top Twenty regression directories per module == The Top Twenty were somewhat misleading as I only looked at the 4 level dirs. Some of our source is actually only 3 levels deep in the tree, so here is the update. I also used the new lcov numbers from this week this time and added a column with regressions per executable KLOC (the number from LCOV ignoring comments, includes and empty lines) as last column. So here are the fixed regression hotspot top twenty: Calc: 171 sc/source/core/data 67.4% (31467/4) 3.66 73 sc/source/core/tool 55.4% (20145/36365) 2.01 59 sc/source/filter/xml57.4% ( 9822/17123) 3.45 58 sc/source/ui/view 30.8% (12092/39254) 1.48 33 sc/source/filter/excel 61.1% (18616/30464) 1.08 22 sc/source/filter/oox53.4% ( 7694/14421) 1.53 22 editeng/source/editeng 31.9% ( 760/ 2385) 9.22 20 sc/source/ui/docshell 46.9% ( 6399/13648) 1.47 Writer: 168 writerfilter/source/rtftok 90.7% ( 4230/ 4664) 36.02 70 writerfilter/source/dmapper 84.5% (10492/12415) 5.64 59 sw/source/core/layout 75.2% (20352/27075) 2.18 53 sw/source/filter/ww872.2% (27691/38375) 1.38 47 sw/source/core/txtnode 71.9% ( 6383/ 8883) 5.29 25 sw/source/core/doc 50.7% (13300/26229) 0.95 21 sw/source/core/unocore 65.2% (16993/26058) 0.81 Base: 17 dbaccess/source/core/api53.0% ( 5236/ 9886) 1.75 LibreOffice 28 vcl/source/window 43.9% (13524/30837) 0.91 28 vcl/source/gdi 38.7% ( 929/ 2399) 11.67 27 svx/source/svdraw 40.1% (14397/35938) 0.75 19 sfx2/source/doc 48.2% ( 7731/16052) 1.18 Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] Regression hotspots updated
Hi, I just updated the regression hotspots page: https://wiki.documentfoundation.org/Development/RegressionHotspots Here are some insights of what changed since the last run one year ago == Top Ten regression modules changes == sfx2 is now at position 6, was at 8. xmloff is now at position 7, was at 6. cui is now at position 8, was at 11. sd is now at position 9, was at 10. editeng is now at position 10, was at 7. connectivity was at position 9, is now at 12. == Top Ten regression directories changes == sc/source/core/toolis now at position 2, was at 6. sc/source/filter/xml is now at position 4, was at 2. sw/source/filter/ww8 is now at position 6, was at 7. sw/source/core/txtnode is now at position 7, was at 4. sw/source/core/doc is now at position 9, was at 11. sc/source/filter/oox was at position 9, is now at 11. == Top Twenty regression directories per module == (ignoring the $module/qa/entries) numbers after the path are (old) lcov line coverage numbers for these[1]. Calc: 171 sc/source/core/data 66.2% (30172/45581) 73 sc/source/core/tool 51.2% (18017/35218) 59 sc/source/filter/xml 55.6% ( 9545/17165) 58 sc/source/ui/view 30.4% (11770/38769) 33 sc/source/filter/excel59.9% (17929/29944) 22 sc/source/filter/oox 41.1% ( 6535/14185) 20 sc/source/ui/docshell 46.1% ( 6288/13639) 18 sc/source/ui/unoobj 68.3% (16252/23790) 13 sc/source/ui/app 23.2% ( 1418/ 6112) 12 sc/source/ui/dbgui 0.5% ( 37/ 7314) Writer: 59 sw/source/core/layout 72.9% (19496/26740) 53 sw/source/filter/ww8 72.2% (27691/38375) 47 sw/source/core/txtnode70.1% ( 6186/ 8819) 25 sw/source/core/doc47.0% (12326/26198) 21 sw/source/core/unocore66.4% (17607/26503) 14 sw/source/core/crsr 39.4% ( 3008/ 7636) 11 sw/uiconfig/swriter/ui- (-/-) Base: 17 dbaccess/source/core/api 41.3% ( 4094/ 9923) Impress: 15 sd/source/ui/view 23.6% ( 4628/19619) LibreOffice 13 vcl/source/filter/wmf 69.7% ( 3349/ 4802) Areas in this list with low test coverage might be good candidates for additional tests as per tdf#66750. Best, Bjoern [1] http://dev-builds.libreoffice.org/lcov_reports/master~2014-11-02_22.37.32/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] make check / dbgutil performance ...
Hi, On Fri, Jun 05, 2015 at 11:56:09AM +0100, Michael Meeks wrote: Without dbgutil we get: real 12m45.145s user 28m47.321s sys 2m34.849s Which is better, but still not 3x minutes. On a slow machine, things are slow. How does it compare to just relinking LibreOffice libs once on that machine? Thats IMHO a goal: to be roughly in the same ballpark. Then again - I don't have an 8x core i7 - which no matter how apparently cheap they are 2nd hand doesn't seem to me that reasonable. Why? It would be an interesting thing to ask around for with LibreOffice developers, but my gut feeling is that the 'has to compile on the notebook that I take aorund the world'-requirement is more one from sponsored developers, while our volunteer contributors often do their compiles at home on a desktop machine ... So - it seems to me that we could usefully invest in improving 'make check' performance; not least by loosing 'sleeps' - I guess more profiling is in order. Maybe, maybe not. If a 'make check PARALLELISM=' is slower/faster by roughly the same ratio between machines, it seems it becomes CPU-bound rather quickly. The numbers from my other mail: make check : 4m36.399s make check PARALLELISM=: 3m 9.598s suggest that there is not much to gain beyond 8x parallelism -- thus there is not much idling then. Also you said the last processes hanging around for you were cppunittesters processes, which should be idlefree. Oh ! and - I suspect the ~3x slower dbgutil issue can be fixed with this easy hack: https://bugs.documentfoundation.org/show_bug.cgi?id=91872 Which is also rather easy I hope. Yep, there is some hope there. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] make check / dbgutil performance ...
Hi, On Fri, Jun 05, 2015 at 02:27:44PM +0300, Tor Lillqvist wrote: Exactly the opposite here. I do paid work on my desktop machine(s), and just light mostly unpaid (or at least not paid by customers) hacking at hackfests or conferences (well, the LO one) on my laptop. Well, we have these awesome on-demand ec2 images by Cloph, which should blow even the newest and fastest notebooks out of the water performance-wise very easily. Being the old grognard I am I have to admit to newer have used them myself, however. Note to self: Lead by example and use one on the Hamburg Hackfest. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Fri, May 29, 2015 at 10:02:56AM +0100, Michael Meeks wrote: It is clearly great to run 'make check' before pushing (just fixing some results from CI) - however, to assume that everyone has a 32 core machine (I have 4 not-so-strong cores) 32/4 * 2m - 16m (not so far from 15 minutes ;-). Eh, missed this mail. No I am not assuming that. See my other mail: with the split-up of the unoapi tests its down 3 minutes -- about the same as (re-)linking a non-debug build and way faster than (re-)linking a debug build. On an antique notebook with a mid-level second generation mobile i7 you get below 400EUR on ebay. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Fri, May 29, 2015 at 02:37:31AM +0200, Bjoern Michaelsen wrote: ... brings 'make check' down to 2m6s on big Bertha. For comparison: [...] that is, just relinking (most) LibreOffice libs takes 2m26s on that machine without symbols (assume more than 10 minutes with symbols). Given this relation, there is no excuse to not run 'make check' anymore at least before pushing -- if there ever was one. Addendum: And this is hardly something you need big Bertha for. On my ancient Lenovo W520 with a i7-2720QM, the equvalent you easily find on ebay for around 400EUR[1]: make check : 4m36.399s make check PARALLELISM=: 3m 9.598s for comparison: find instdir/ -name '*lo.so'|xargs rm; time make: 2m35.287s Best, Bjoern [1] http://www.ebay.de/itm/Dell-Latitude-E6520-i-7-2720QM-8GB-Ram-250GB-Hard-DriveWin-7-Pro-DVD-Burner-/251971816621?pt=LH_DefaultDomain_0hash=item3aaab0ccad http://www.ebay.de/itm/Dell-Latitude-E6420-14-inch-Quad-Core-i7-2720QM-Software-Loaded-Win-7-Ult-Laptop-/111673406542?pt=LH_DefaultDomain_0hash=item1a0040f44e http://www.ebay.de/itm/Lenovo-ThinkPad-T520-Core-i7-2720QM-2-2Ghz-4GB-RAM-500GB-HDD-No-15-/151658617035?pt=LH_DefaultDomain_3hash=item234f8ed8cb http://www.ebay.de/itm/Dell-Precision-M4600-Quad-Core-i7-2820QM-8GB-RAM-500GB-NVIDIA-1000M-/221708776802?pt=LH_DefaultDomain_77hash=item339edf7562 http://www.ebay.de/itm/HP-Elitebook-8560w-XX058AV-i7-2820QM-2-3-GHz-Nvidia-Quadro-2000M-B-Ware-/161709959563?pt=LH_DefaultDomain_77hash=item25a6aa298b http://www.ebay.de/itm/Fujitsu-Celsius-H710-Intel-Core-i7-2820QM-160GB-SSD-8GB-IRMC-Win-7-Pro-/321742632014?pt=LH_DefaultDomain_77hash=item4ae95af44e ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, May 28, 2015 at 06:01:33PM +, Noel Grandin wrote: Wasn't someone going to look at speeding that up? Make check is not currently making very good use of multiple cores and it has a long tail where only one or two cores are busy. I cant fully confirm that -- at least not combined with Michaels 15 minutes number. Good ol' big Bertha with two Opteron 6272s has 32 cores, but mediocre single-threaded performance compared with some of todays offerings. Still[1]: -j real 5m 9.091s user25m12.250s sys 2m53.420s -j32 real 5m30.133s user29m46.310s sys 3m10.660s -j8 real 6m35.434s user19m36.700s sys 2m 6.390s -j1 real34m11.814s user17m51.990s sys 1m52.470s (all above along with moderate desktop use alongside: Firefox, mplayer audio streaming etc. -- so not too scientific.) And with this I see a lot of processes running parallel till the end. This suggests to me that the stuff is quite parallelized -- however none of the testing threads seem to be CPU-bound rather the Java-stuff seems to be IO bound (for IPC?) with the slowest test unit taking ~5 minutes. Thus even 32 jobs or more dont seem to keep more than one core busy. At least for people with a meager duo-core laptop or somesuch, this suggests you should try: time make check PARALLELISM= # aka forkbomb me please And if that doesnt explode your RAM, it should help you quite a bit and you should end up with 5 minutes for 'make check' -- quite independant of your hardware, as much of that seems IO-bound idling. If we want to cut down on that 5 minutes, we would need to touch the JunitTest internals. Best, Bjoern [1] As a sidenote: I noted that linking with debug symbols takes at least 4 times as long as without debug symbols. Given that linking happens at the end of the build with a narrow dependency tree left (as libraries are daisy-chained dependency-wise for linking), you are really penalized for building with symbols when you dont need those, as it can easily dry out paralellism. So dont do that: Rather than building with symbols everywhere and then skipping on tests, better build without symbols unless you are debugging, but _run the tests_. [2] On my ancient notebook with a i7-2720QM (a modern 4th gen i7-4770HQ is at least 50% faster at the same speed) I find the following with disabling Junittest_toolkit_unoapi as it was failing on that checkout. time make check PARALLELISM=: reall5m15.351s user15m52.808s sys 1m10.073s time make check (thus -j8): real 6m2.806s user14m32.157s sys 1m1.861s time make check PARALLELISM=1: real41m 7.984s user27m33.174s sys 1m13.949s ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, May 28, 2015 at 10:40:40PM +0200, Bjoern Michaelsen wrote: And with this I see a lot of processes running parallel till the end. This suggests to me that the stuff is quite parallelized -- however none of the testing threads seem to be CPU-bound rather the Java-stuff seems to be IO bound (for IPC?) with the slowest test unit taking ~5 minutes. Thus even 32 jobs or more dont seem to keep more than one core busy. So, I has a look at what is so slow in subsequentcheck: sc_unoapi4m21.137s sw_unoapi3m34.494s toolkit_unoapi 3m18.056s forms_unoapi 2m51.588s sw_complex 1m 6.937s framework_unoapi 1m 2.938s svx_unoapi 0m40.205s sd_unoapi0m38.568s chart2_unoapi0m37.695s xmloff_unoapi0m29.696s ucb_unoapi 0m25.288s starmath_unoapi 0m24.856s pragmatically splitting up the first four: https://gerrit.libreoffice.org/#/c/15959/ brings 'make check' down to 2m6s on big Bertha. For comparison: find instdir/ -name '*lo.so'|xargs rm; time make that is, just relinking (most) LibreOffice libs takes 2m26s on that machine without symbols (assume more than 10 minutes with symbols). Given this relation, there is no excuse to not run 'make check' anymore at least before pushing -- if there ever was one. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] organizing our crasher bugs ?
Hi, On Wed, May 27, 2015 at 04:36:01PM +0200, Bjoern Michaelsen wrote: Hi, On Wed, May 27, 2015 at 03:25:24PM +0100, Caolán McNamara wrote: What would work ideally for me is to someone get the subset of all crashes that are ~100% reproducible under Linux and ordered by the number of steps required to reproduce. Any ideas on how to generate that subset ? Another hint of a good, clean, solvable bug is a limited number of comments: https://bugs.documentfoundation.org/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDcolumnlist=product%2Ccomponent%2Cassigned_to%2Cshort_desc%2Cchangeddate%2Cop_sys%2Clongdescs.countlist_id=539737product=LibreOfficequery_format=advancedresolution=---short_desc=crashshort_desc_type=allwordssubstr once you have more than 10 comments on a bug, there is a high chance of some can reproduce on $foo, cant reproduce on $bar ping-pong going on. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Try not to reopen bugs when anything more than a trivial amount of time has passed
On Tue, Mar 24, 2015 at 07:33:03PM +0100, Bjoern Michaelsen wrote: all bugs(*). One could have a bot setting bugs from RESOLVED to VERIFIED though, if there is not objection (verified by silent approval) ... after the suggested a month timeframe, that is obviously. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] DLP Projects as products?
Hi, On Thu, Feb 12, 2015 at 04:52:45PM +0100, David Tardon wrote: I do not even quite understand what you mean by it. To merge all the libraries into one? Or to always release everything whether there has been any change or not? The latter would be a starting point. You will hardly get a article about a new version of libmwaw or libcdr on their own. Not TDF does do any press release about individual library releases. You see however e.g. LibreOffice, GNOME, KDE, Java releasing stuff as a set and thus gaining enough critical mass for some media coverage -- even for functionality that is not always directly related. Anyway: As said, not a QA-topic, so not really for this list. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] DLP Projects as products?
Hi, On Thu, Feb 12, 2015 at 01:46:24PM +0100, David Tardon wrote: I disagree. The libraries are separate projects, not components of a single project. Also, an user reporting a bug for one of the libraries might not even know about DLP. So hiding the libraries under DLP label would not be user friendly. True from a technical point of view. But being the devils advocate here: Maybe DLP should consider syncing these separate projects and release them as a consistent collection. If anything, LibreOffice (and in a different realm: systemd) has shown this to have significant marketing, branding and release engineering advantages. This really doesnt belong here, its hardly a QA topic. But maybe DLP projects should at least consider the thought. Justsaying. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] that walrus
On Sat, Jan 31, 2015 at 07:25:45AM -0700, bfoman wrote: Bjoern Michaelsen wrote He/She might reappear possibly though now that this is our Bugzilla: e.g. for bug hunting sessions. Those have hunter walrus (https://wiki.documentfoundation.org/images/4/44/Bughuntban4.4.png). No, I meant not having a Walrus on Bugzilla, _except_ for bug hunting sessions. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] suggestion for weekly-bug-summary
On Fri, Jan 30, 2015 at 07:56:57AM +0100, Cor Nouws wrote: Joel Madero wrote on 30-01-15 00:13: Would that be good possible? I agree that it would be good it is possible. Can I change add a query myself to that page? Just a note hinting at what should be obvious: If we modify anything, that stuff needs to be in git on gerrit. No exceptions. With the usual $foo: LICENSE, README explaining how that stuff is deployed etc. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] suggestion for weekly-bug-summary
Hi, On Thu, Jan 29, 2015 at 03:13:18PM -0800, Joel Madero wrote: I agree that it would be good it is possible. I highly recommend we create a new product bugzilla where we can easily track these enhancement requests...else they are likely to get lost in the abyss. Nope. Bugzilla is Infra. Infra is on Redmine. Lets not make exceptions to exceptions. Its already complicated enough. see: https://redmine.documentfoundation.org/issues/1055#note-1 http://nabble.documentfoundation.org/TDF-bugzilla-bug-report-td4137958.html Still, creating enhancement suggestions _if_ they are reasonably ressourced, or the reporter commits him/herself to it is of course great. But that has to happen on Redmine. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] suggestion for weekly-bug-summary
Hi, On Thu, Jan 29, 2015 at 04:14:24PM -0800, Joel Madero wrote: I've never been a fan of this split to begin with. Having a much less visible means of suggesting enhancement requests or bugs pretty much just sucks. Just speaking for myself, I'm very unlikely to report any enhancement requests about bugzilla on redmine... Oh, hate the split too. The split will not go away easily though (I tried. Hard.). Yeah, sucks. Still, the best we can do now is have a clear cut rather than fractured border between the two. So we're only tracking enhancement requests if the reporter can either (1) do it themselves; or (2) they can show that it's reasonably resourced? I can't imagine a similar strategy working for LibreOffice itself - we might as well close 99% of enhancement requests. I don't get why we'd have two different philosophies just because one is infra and the other is something else? So, maybe Im overcautious. ;) As an exaggeration: There is a risk that we end up with 20 people working on making our Bugzilla nice and beautiful and 1 guy working on triaging LibreOffice. Also note that all customization cumulates to create extra pains during updates etc. IMHO we should just keep in mind to keep the fixed costs of running our Bugzilla constant and rather low[1]. Best, Bjoern [1] For example that we ended up with a Redmine/Bugzilla split (which is already a simplification over the mess we had before that) is ultimately a result of bit too much fast-and-loose play with extending, creating and customizing services. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Keyword bisected
Hi, On Mon, Jan 05, 2015 at 08:23:20AM -0800, Joel Madero wrote: A couple people have told me they use the keyword to indicate that the exact (or nearly the exact) commit has been identified. I use it like that. If this is true...it's good to have (and would be another potential easy hack to move bibisected to bisected), but we need to share this information with developers so that it's actually useful information. Else, if developers are just querying for bibisected in whiteboard, they are going to miss bisected in keyword FWIW, I used it only on bibisected bugs, so at least where I set it, the bug is whiteboard: bibisected keyword: bisected in the end, so that bisected bugs are a subset of the bibisected bugs. This was done when I did the other swipe over regressions etc. and was discussed on the ESC: http://nabble.documentfoundation.org/minutes-of-ESC-call-td4127344.html Back then, I looked for all the bibisected Writer regressions and identified those that have a suspected single commit identified, because I wanted to have an idea of how many bugs are triaged down to one commit. For Writer, it was quite a huge set of the open bibisected regressions. This is a Good Thing as shows that bibisecting works. This is a Bad Thing, as we likely should be faster/more vicious in evaluating if the commit that caused the regression was worth it (because it e.g. fixed a bigger problem). In some cases, it might make sense to close the bug as WONTFIX, if there is no proper solution, and reverting the guilty commit would bring back bigger issues. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Tue, Dec 23, 2014 at 10:31:35PM +0100, Cor Nouws wrote: One thing that may be handled too: when confirming also check if it worked before (regression or not) and such. True. In the end a fully triaged (aka a bug that a QA guys can do nothing more about and that only can be moved forward by a developer) is either: 1/ a regression, which has been bibisected 2/ a non-regression, missing feature (enhancement) 3/ a non-regression, bug introduced with new feature from the start We have proper tags to identify the first two of the above, but nothing to tag the last group. If we _had_ a whiteboard status for number three too, we could query for confirmed bugs that are: - not a bibisected regression - not an enhancement request - not marked as a bug introduced with a new feature from the start and have a list of confirmed bugs that QA can still help about. As such Id suggest maybe a whiteboard status newfeaturebug for this. Opinions? Best, Bjoern P.S.: Note there is some wiggle room in distingushing group 2/ and 3/. IMHO if a developer of a feature says its group 2/ (aka that it was not in the planned scope of the new feature) that should be accepted in general (and possibly also documented that way). ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Wed, Dec 24, 2014 at 12:13:57PM +0100, Robert Großkopf wrote: Hi Bjoern, True. In the end a fully triaged (aka a bug that a QA guys can do nothing more about and that only can be moved forward by a developer) is either: 1/ a regression, which has been bibisected 2/ a non-regression, missing feature (enhancement) 3/ a non-regression, bug introduced with new feature from the start How would you call a bug inherited from OOo? 4/ Inherited from OOo ;) Forgot that one, but that is also trivially queryable, so doesnt change the conclusion we only need a way to tag bugs in group 3. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] mab4.2 to mab4.3 migration almost over
Hi, On Wed, Dec 17, 2014 at 11:09:37AM -0800, Joel Madero wrote: Well when we move to our own bug tracker we are hoping to abandon MAB completely and just use priority/importance - as these will be locked out to regular users so we can make sure they are objective and accurate. So...hopefully soon the problem is gone :-D FWIW, I just did a run for: https://bugs.freedesktop.org/show_bug.cgi?id=84480 and Fdo should be completely consistent in that all MAB are priority highest and all non-MAB are not priority highest. Also there seems actually little abuse by people in the priority field -- the fear of people making bugs priority highest willy-nilly (and for some reason not doing so with MABs) seems rather baseless. Thus I think we could kill MABs right now and use priority proper today, if we want to. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Bibisect 4.4
On Thu, Dec 11, 2014 at 03:17:28PM -0500, Robinson Tryon wrote: Bibisect 4.4 has been updated and is available from the dev-downloads server as bibisect-44.tar.xz. Information about bibisecting here: https://wiki.documentfoundation.org/QA/HowToBibisect#Versions Awesome, thanks! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] 4.4 refactorings and BHS (was: minutes of ESC call ...)
Hi, On Thu, Nov 13, 2014 at 04:13:33PM +, Michael Meeks wrote: * QA (Robinson) There is a Bug Hunting Session for 4.4 coming up next week. If you did any bigger refactoring or other work that primarily can be assumed to affect a specific area of usecases, please add this to: https://wiki.documentfoundation.org/BugHunting_Session_4.4.0.0#What_to_test so we can get early warning on e.g. regressions by some more focussed testing. Of course, if you did something that is not only a refactoring bug actually brings new features, you are invited to add this to: https://wiki.documentfoundation.org/ReleaseNotes/4.4 so that marketing can use it too and e.g. prepare cute screenshots. @Michael: Can we add that reminder for the next ESC call too? Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] 4.4 refactorings and BHS (was: minutes of ESC call ...)
On Fri, Nov 14, 2014 at 03:42:16PM +0100, Sophie Gautier wrote: Maybe it would be easier if I add the test cases to MozTrap? there could be also a follow-up through the beta/rc/final. Thank you, that would be great! I was suggesting to just edit the wiki as telling hackers to enter stuff in MozTrap likely earns us just a few groans mumbling yet another login/account. Speaking of that: If people come forward during the ESC call with stuff done for 4.4 we should just put that in the minutes -- we can copy it over to the Wiki/MozTrap later. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice 4.4 alpha 2 bibisect repo
Hi all, I am currently uploading the intermediate LibreOffice 4.4~alpha2 bibisect repo to: http://people.canonical.com/~bjoern/bibisect/bibisect-44alpha2only.tar.xz http://people.canonical.com/~bjoern/bibisect/bibisect-44alpha2only.tar.xz.sig it should be finished in ~1 hour. Note the baseline for this one was updated to Ubuntu 14.04 LTS. Also note that for 4.4~beta2 we expect a new baseline anyway as per: https://redmine.documentfoundation.org/issues/790 and those will then be provided by Robinson. Best, Bjoern P.S.: TBH, I didnt even started LibreOffice once from this repo, simply too many things on my plate right now. Caveat emptor. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Migration of dev-downloads to new infrastructure - Planned DOWNTIME
On Mon, Nov 10, 2014 at 02:14:40PM +0100, Alexander Werner wrote: the dev-downloads VM will be migrated to our new infrastructure on Tuesday, 11 November, thefore there will be a downtime starting at about 0900UTC and ending around 2300UTC. As that is a prime download location for bibisect repositories, could you put a fat red warning note on: https://wiki.documentfoundation.org/QA/HowToBibisect#Versions temporary during the downtime (best with a link to your announce mail)? Thanks. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] No activity warnings - EasyHacks
On Tue, Oct 28, 2014 at 10:18:04PM +0100, Jan Holesovsky wrote: But that's probably hard to do ATM, so I'd avoid any retest pings there; or at least phrase them differently - in the Easy Hacks, the pings shouldn't be about retesting, but more about the review of the Easy Hack itself, because the fact that it was not taken might indicate that it is not an Easy Hack in the first place :-) Indeed. For everything else, lets please refrain from adding automated messages to EasyHacks, if possible -- they are supposed to be read by an enthusiastic new contributor and too many comments (esp. over 10 comments and automated ones) are quite a demotivating turn-off. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-10-16
On Fri, Oct 17, 2014 at 11:13:12AM +0200, Jan Holesovsky wrote: * Open-source related projects for a local university (Jacobo) + ~200-300 hours projects sought + ideas appreciated! + please send to the ML too :-) (Norbert) Two ideas from the build system world: - 1/ Replace all custom shell tooling (sed/grep/gawk/perl horrors) and consolidate on either native (C/C++) code (see e.g. concat-deps) or _one_ and only one consolidated solution beyond that, likely Python3 (as we are bundling that and it is a good crossplatform superset of the POSIX shell-world). Bootstrapping on Windows would then likely be: Install native Python3, execute Python script that sets up the rest. rationale: As we already use a native GNU make on Windows, with this we could remove our dependency on cygwin as Python3 is available natively on Windows (and all other platforms). - 2/ Generate native Microsoft VS Project files from the gbuild description for our own native C/C++ files. This: https://bugs.freedesktop.org/show_bug.cgi?id=70414 https://www.youtube.com/watch?v=Xn3CtIrMpIAhd=1 would be the starting point. rationale: The aim would not be to do full release builds from these (see 1/ about that), but should allow patching and rebuilding one specific library, which then can be pushed to gerrit. If we have this we could make the generation of these project files part of the Windows build and deliverables (as some kind of sdk). Windows people could use these to patch some libs of their version of LibreOffice (without a full rebuild and thus without cygwin). 2/ is the one with the more immediate payoff: I might severly lower the barrier to entry for new contributors on Windows at least for patches with a limited scope. With gerrit builders we have the infra in place to verify and handle such changes without too much extra work. Of course, combined with 1/ it would allow to ultimately move to make all Windows builds without cygwin. Which would be all kinds of awesome for the Windows devs, I guess. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-10-16
On Fri, Oct 17, 2014 at 11:13:12AM +0200, Jan Holesovsky wrote: * LibreOffice 4.4 bibisects repo creation (Bjoern) + Bjoern creating, but Robinson should take over + but has time for that? - bugzilla migration a priority... (Bjoern) + Bjoern can do that at the time of the tag, but then is traveling Big Bertha is still churning on that, will likely be finished soon. But I wont find time to finalize that repo for upload (besides there isnt yet a alpha1 tag anyway). ETA for the alpha bibisect repo will thus be around 2014-10-31. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] ping to retest old bugs
On Thu, Oct 16, 2014 at 10:47:05PM -0700, Joel Madero wrote: I'm honestly hesitant to do any more of this kind of thing with the email notification on. Devs hate it, users hate it, etc . . . Our bug tracker is making progress, IMHO this can wait until we get it fully up. Just my two cents. Indeed, this can wait a few more weeks for the migration. OTOH, just thinking aloud: _After_ the migration, doing such a reping might be a cunning way to get people into reactivating their accounts on our own bugtracker ... Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-10-16
Hi, On Fri, Oct 17, 2014 at 11:47:30AM +0200, Stephan Bergmann wrote: Would not the best thing to do be to do bibisect builds on the release baseline, as is done for the TDF builds? That way, the builds should work on as many machines as possible. As discussed explicitly in the call: I have no time at all for that, you are free to volunteer. Right now, I plan to do the alpha1 bibisect build to keep Robinsons backs free for the Bugzilla migration. Robinson will then take over for the beta/branchoff builds of bibisect, and if you think its worth setting up a baseline chroot for the bibisects then, that might be an option (possibly redoing the stuff I build on that baseline). Then again, as per: https://wiki.documentfoundation.org/QA/HowToBibisect#Manual_setup_.28download_a_tarball.29 there are currently _no_ reports of recent build being not universal. Michael Stahl once ranted about the old LibreOffice 3.5 build as they linked against a system libjpeg, but that was never affected the build after that. If anyone is volunteering to rebuild LibreOffice 3.5 without libjpeg, you are invited as Michael never did that[1]. ;) Best, Bjoern [1] Which is even somewhat understandable, given the quality of our build back then, needing hotpatching like this: https://gerrit.libreoffice.org/gitweb?p=dev-tools.git;a=blobdiff;f=bibisect/build.sh;h=42427226aaa73b4764d0181f5c40aa4105809b67;hp=831436cc138737a88647893e29af20ecd4477731;hb=80e0a38aae8ed422e8c4350ef3a234bc92f504fb;hpb=f6bdfcfce464f40e51a8c1ff7aca9b08a93f4cb8 ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-10-16
On Fri, Oct 17, 2014 at 11:01:51AM -0400, Terrence Enger wrote: I have created a debian-sid chroot environment to avoid complaints about old libraries from the bibisect versions. For example in debian-wheezy (i.e., stable), 43all version latest complains: The alpha1 bibisect update is already building, I hope I can upload it still before travelling. Beyond that: Volunteers welcome, Im handing this over to Robinson for the 4.4 beta anyway -- after the Bugzilla migration, which currently has priority for Robinson. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-10-16
On Fri, Oct 17, 2014 at 11:13:12AM +0200, Jan Holesovsky wrote: + need a bugzilla query for the bugs that have been bisected to a single commit (Miklos) AI + can do that (Bjoern) + we have a keyword bisected, can use that for those with exact commit + done: https://bugs.freedesktop.org/buglist.cgi?bug_status=NEWcomponent=Writerkeywords=bisected%2C%20keywords_type=allwordslist_id=481507product=LibreOfficequery_format=advanced @Robinson: Can you document/discuss that workflow with the QA team (aka: keyword bisected - we think its this _one_ commit?). It might be helpful and could then be used on other components too. (Note: I only walked through the writer regressions). Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] ping to retest old bugs
Hi, On Thu, Oct 16, 2014 at 04:03:47AM +0200, Tommy wrote: your bug report has shown no activity in the last 6 months. newer LibO releases with hundred of bugifixes and new features have been releases meanwhile, so please retest with current LibO release (4.3.2.2) and give feedback of the actual status of the bug. if bug is gone set status to RESOLVED WORKSFORME. if bug is still present leave status UNCHANGED and drop a new comment telling the LibO version where you retested and reproduce it Whatever you guys decide on this -- the text definitively need a hint like: Regardless of what you find in newer versions, the VERSION fields should stay at the _first_ version that showed the buggy behaviour. Otherwise this will create more work than it will remove. ;) Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] UNCONFIRMED bug count below 800
On Thu, Oct 16, 2014 at 03:57:14AM +0200, Tommy wrote: On Thu, 16 Oct 2014 03:53:47 +0200, Tommy ba...@quipo.it wrote: the QA team broke another mileston. we are back below 800, see: https://bugs.freedesktop.org/report.cgi?y_axis_field=bug_statusquery_format=report-tableproduct=LibreOfficeformat=tableaction=wrap the trend is good as well: https://bugs.freedesktop.org/reports.cgi?product=LibreOfficedatasets=UNCONFIRMEDdatasets=NEEDINFO thumbs up!!! a better chart here: https://bugs.freedesktop.org/reports.cgi?product=LibreOfficedatasets=UNCONFIRMED even better: as csv (attached) Best, Bjoern Date\Series,libreoffice-unconfirmed 2013-08-02,984 2013-08-03, 2013-08-04, 2013-08-05, 2013-08-06, 2013-08-07, 2013-08-08, 2013-08-09,979 2013-08-10, 2013-08-11, 2013-08-12, 2013-08-13, 2013-08-14, 2013-08-15, 2013-08-16,1022 2013-08-17, 2013-08-18, 2013-08-19, 2013-08-20, 2013-08-21, 2013-08-22, 2013-08-23,1050 2013-08-24, 2013-08-25, 2013-08-26, 2013-08-27, 2013-08-28, 2013-08-29, 2013-08-30,1090 2013-08-31, 2013-09-01, 2013-09-02, 2013-09-03, 2013-09-04, 2013-09-05, 2013-09-06,1128 2013-09-07, 2013-09-08, 2013-09-09, 2013-09-10, 2013-09-11, 2013-09-12, 2013-09-13,1155 2013-09-14, 2013-09-15, 2013-09-16, 2013-09-17, 2013-09-18, 2013-09-19, 2013-09-20,1178 2013-09-21, 2013-09-22, 2013-09-23, 2013-09-24, 2013-09-25, 2013-09-26, 2013-09-27,1187 2013-09-28, 2013-09-29, 2013-09-30, 2013-10-01, 2013-10-02, 2013-10-03, 2013-10-04,1187 2013-10-05, 2013-10-06, 2013-10-07, 2013-10-08, 2013-10-09, 2013-10-10, 2013-10-11,1170 2013-10-12, 2013-10-13, 2013-10-14, 2013-10-15, 2013-10-16, 2013-10-17, 2013-10-18,1171 2013-10-19, 2013-10-20, 2013-10-21, 2013-10-22, 2013-10-23, 2013-10-24, 2013-10-25,1164 2013-10-26, 2013-10-27, 2013-10-28, 2013-10-29, 2013-10-30, 2013-10-31, 2013-11-01,1201 2013-11-02, 2013-11-03, 2013-11-04, 2013-11-05, 2013-11-06, 2013-11-07, 2013-11-08,1200 2013-11-09, 2013-11-10, 2013-11-11, 2013-11-12, 2013-11-13, 2013-11-14, 2013-11-15,1205 2013-11-16, 2013-11-17, 2013-11-18, 2013-11-19, 2013-11-20, 2013-11-21, 2013-11-22,1129 2013-11-23, 2013-11-24, 2013-11-25, 2013-11-26, 2013-11-27, 2013-11-28, 2013-11-29,955 2013-11-30, 2013-12-01, 2013-12-02, 2013-12-03, 2013-12-04, 2013-12-05, 2013-12-06,972 2013-12-07, 2013-12-08, 2013-12-09, 2013-12-10, 2013-12-11, 2013-12-12, 2013-12-13,953 2013-12-14, 2013-12-15, 2013-12-16, 2013-12-17, 2013-12-18, 2013-12-19, 2013-12-20,971 2013-12-21, 2013-12-22, 2013-12-23, 2013-12-24, 2013-12-25, 2013-12-26, 2013-12-27,870 2013-12-28, 2013-12-29, 2013-12-30, 2013-12-31, 2014-01-01, 2014-01-02, 2014-01-03,752 2014-01-04, 2014-01-05, 2014-01-06, 2014-01-07, 2014-01-08, 2014-01-09, 2014-01-10,747 2014-01-11, 2014-01-12, 2014-01-13, 2014-01-14, 2014-01-15, 2014-01-16, 2014-01-17,779 2014-01-18, 2014-01-19, 2014-01-20, 2014-01-21, 2014-01-22, 2014-01-23, 2014-01-24,790 2014-01-25, 2014-01-26, 2014-01-27, 2014-01-28, 2014-01-29, 2014-01-30, 2014-01-31,787 2014-02-01, 2014-02-02, 2014-02-03, 2014-02-04, 2014-02-05, 2014-02-06, 2014-02-07,833 2014-02-08, 2014-02-09, 2014-02-10, 2014-02-11, 2014-02-12, 2014-02-13, 2014-02-14,877 2014-02-15, 2014-02-16, 2014-02-17, 2014-02-18, 2014-02-19, 2014-02-20, 2014-02-21,925 2014-02-22, 2014-02-23, 2014-02-24, 2014-02-25, 2014-02-26, 2014-02-27, 2014-02-28,937 2014-03-01, 2014-03-02, 2014-03-03, 2014-03-04, 2014-03-05, 2014-03-06, 2014-03-07,953 2014-03-08, 2014-03-09, 2014-03-10, 2014-03-11, 2014-03-12, 2014-03-13, 2014-03-14,925 2014-03-15, 2014-03-16, 2014-03-17, 2014-03-18, 2014-03-19, 2014-03-20, 2014-03-21,949 2014-03-22, 2014-03-23, 2014-03-24, 2014-03-25, 2014-03-26, 2014-03-27, 2014-03-28,967 2014-03-29, 2014-03-30, 2014-03-31, 2014-04-01, 2014-04-02, 2014-04-03, 2014-04-04,1026 2014-04-05, 2014-04-06, 2014-04-07, 2014-04-08, 2014-04-09, 2014-04-10, 2014-04-11,1056 2014-04-12, 2014-04-13, 2014-04-14, 2014-04-15, 2014-04-16, 2014-04-17, 2014-04-18,1132 2014-04-19, 2014-04-20, 2014-04-21, 2014-04-22, 2014-04-23, 2014-04-24, 2014-04-25,1159 2014-04-26, 2014-04-27, 2014-04-28, 2014-04-29, 2014-04-30, 2014-05-01, 2014-05-02,1118 2014-05-03, 2014-05-04, 2014-05-05, 2014-05-06, 2014-05-07, 2014-05-08, 2014-05-09, 2014-05-10, 2014-05-11, 2014-05-12, 2014-05-13, 2014-05-14, 2014-05-15, 2014-05-16,1187 2014-05-17, 2014-05-18, 2014-05-19, 2014-05-20, 2014-05-21, 2014-05-22, 2014-05-23,1165 2014-05-24, 2014-05-25, 2014-05-26, 2014-05-27,
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Oct 09, 2014 at 04:35:12PM +0100, Caolán McNamara wrote: Wouldn't it be nice if the bugs could be split into two categories of 100% reproducible and not, and script the 100% reproducers and automatically re-run the script on each milestone to see which ones got fixed in passing. Though I guess in practice that would depend on reliable gui automation in a lot of cases. Hmm, I kinda like that. Just wondering: Maybe we should have an EasyHack to write tests for these regressions? At least some of those should be possible to recreate in good test code. For one, this would give us relevant information: 1/ Is this regression really still around on master 2/ Should allow full-auto bibisect to the commit introducing the trouble 3/ Is this a Heisenbug? Does it happen on all platform? etc. And fianlly: We will have a test in the end even after this is fixed. After all, we all know that the motivation to write a test drops even harder once there is a fix as this is not a problem anymore. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Update to wiki Development/Java page
Hi, On Sun, Sep 07, 2014 at 05:22:20AM -0700, Owen Genat wrote: I have just made an update to the wiki Development/Java page: https://wiki.documentfoundation.org/Development/Java Most of that code is not shipped production code, but testcode etc. -- I added a commented stripped down list at: https://wiki.documentfoundation.org/Development/Java#Which_directories_contain_.2A.java_files.3F Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
Hi, On Thu, Sep 25, 2014 at 03:36:34PM +0100, Michael Meeks wrote: + how is redmine used for QA ? (Robinson) + specific admin pieces tracked in there. + happy to use bugzilla for that purpose + might already fit in the existing infra in Redmine ? (Bjoern) + could we merge those close the project ? AI: + move the data across to infra / bugzilla (Bjoern) + easy to do now - only 10x tasks or so. Done now, project QA on RedMine is empty, most of the stuff is on bugzilla: https://redmine.documentfoundation.org/projects/qa/issues The only remaining task is: https://redmine.documentfoundation.org/issues/599 asking Florian to close the project, ideally by keeping existing stuff without allowing new issues filed there. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Sep 25, 2014 at 03:36:34PM +0100, Michael Meeks wrote: + Bjoern re-introduced mergelibs for 4.3.2 + enabled for 4.3.1 without a patch, we need other libs in mergelibs to avoid circular deps. + some interesting bug reports wrt. dbtools moving into mergelibs etc. + anyone interested in investigating ? + mergelibs works nicely from 4.0.x - 4.2.x startup time is visibily faster with it. compressed pkg is 1Mb smaller too ... So, since I had to fiddle with this anyway I did measure cold and hot starts of LibreOffice in an Ubuntu 14.10 VM: cold warm mergedlibs 2.06s ~0.8s no mergedlibs3.46s ~0.8s These times were handstopped, thus likely at least -/+0.2s (thus the warm starts arent really worth anything) -- still a cold start of LibreOffice is some ~70% faster on cold start. This is with a full distro build of 4.3.2.2 with full install (including java-foo) on a 8GB VirtualBox VM running on a i7-2720QM/16GB host. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] MySQL native connector for OS X
On Wed, Sep 24, 2014 at 07:50:56PM -0400, Robinson Tryon wrote: On Wed, Sep 24, 2014 at 7:33 PM, Dan Lewis elderdanle...@gmail.com wrote: Ubuntu version. I seem to recall that build-dep did not install all of the required build environment for me and that I had to add extra stuff. bingo! First and only error: Error running ./autogen.sh line 258. Explanation of the error: Files not found: gstreamer-0.10 gstreamer-0.10-plugins-base-0.10 ... So, what should I do now. My laptop (32r bit) is running Kubuntu 14.04. The build dependencies package on *buntu doesn't include gstreamer stuff. To fix that: sudo apt-get install libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev Alternatively, do: ./autogen.sh --enable-gstreamer --disable-gstreamer-0-10 to use the less horribly outdated gstreamer 1.0 instead of gstreamer 0.10 (as Ubuntu packages do). Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] minutes of ESC call ...
On Thu, Sep 25, 2014 at 03:36:34PM +0100, Michael Meeks wrote: + blog about the sad realities of web plugins (Bjoern) [ writing it right now ] done: http://skyfromme.wordpress.com/2014/09/25/killing-the-npapi-plugin/ Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Suggestion for the use of pre-written responses
Hi, On Wed, Aug 20, 2014 at 04:35:52PM +0400, Jay Philips wrote: So i'd like to propose the creation a wiki page of pre-written responses that we can all use. I have created the wiki page at https://wiki.documentfoundation.org/QA/BugTriage/Pre-Written_Responses and will be adding entries to it, though i have very little knowledge of how best to format the page :D. Please add in your own collection of responses if you have. that is a great idea! Also we might later consider expending it to having them easily selectable from a pulldown etc. (either with e.g. greasemonkey or own-bugzilla), because as important as this is, I personally guess I will not look for the wikipage everytime for a drive-by confirm. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] minutes of the ESC Call 2014-08-14
* Present + Robinson, Miklos, Christian, Bjorn, Michael S, Muthu * Completed Action Items + setup some VM's that can be created on-demand (Cloph) + done for the hackfest, non-public + working on creating a public machine + initial version based on Amazon marketplace Ubuntu 14.04 base, using a community version for upcoming events, which is more freely distributable * Pending Action Items: + ask UX advise wrt. wrench icons (revert or not ?) (Astron) + blog about the sad realities of web plugins (Bjoern) + open-source newer Synezip tests / speak at the conference (Umesh) + Ask for 1-2 more dev-list moderators re-visit next-week (Michael) + contact Michael / the list when students show up (Jan Marek) + help Cloph with the quickstarter disabling (Andras) https://gerrit.libreoffice.org/#/c/10817/ https://gerrit.libreoffice.org/#/c/10669/ * GSOC Update (Cedric) + poke students * Release Engineering update (Christian) + RC2 tagging tommorrow + 4.3.1 RC2 status + Android Remote * support of non-SSE2 capable CPUs + by accident (switch to MSVC 2012) the 4.3 Windows release requires SSE2 + https://bugs.freedesktop.org/show_bug.cgi?id=82430 + https://gerrit.libreoffice.org/#/c/10838/ might help + since these CPUs were made until 2005 most likely users run WinXP should we support them at least as long as WinXP? = reenable non-SSE2 support, but need testers * Crashtest update (Markus) + no Markus (maybe we should broaden the skill base to read these?) * Certification Committee (Stephan/Bjoern/Kendy) + waiting until ~September (nearly there) * commit access confusion: + OTRS finally dead and gone in the docs, I hope (Bjoern) + Norbert set up a branch for Doug, which should nicely solve this for porting patches AI: + porting patches shouldnt be needed anymore on master, see after remaining changes in gerrit (Bjoern) + Samuel: on hold -- too many common mentors/reviewers are on vacation still * USA Hackfest update (Michael?) + Boston Hackfest + hosted by Xamarin, had some engineers come over + some good bugfixing, some good mentoring ... * Hackfests (Bjoern) + Seattle 'Libre-Fest' (Robinson) https://wiki.documentfoundation.org/Events/2014/Seattle_LibreFest + October 26, 2014 + Bug-triaging/Intro-to-community event + Following SeaGL conference + Munich hack-fest (Jan-Marek): http://www.it-muenchen-blog.de/2014/07/bug-squashing-party-2014/ + will have a BSP come-together; if someone says they're coming just show up etc. + November 21st-23rd, 2014 https://wiki.debian.org/BSP/2014/11/de/Munich + we should drop by with 2 or 3 developers, if possible + Toulouse Hackfest ... + Confirmed for Nov. 15-16th + more details: https://wiki.documentfoundation.org/Hackfest/Toulouse2014 + Be great to have -really- easy easy hacks for devs (Bjoern) * QA (Robinson) + UNCONFIRMED count creeping up. Recruiting again + More inquiries re: Windows quickstarter https://bugs.freedesktop.org/show_bug.cgi?id=80927 + Multiple q's and bugs filed re: video playback support in Impress https://bugs.freedesktop.org/show_bug.cgi?id=79546 - OSX (plays in QT, not in LO) + Do we document our policy for video/audio playback? (using system framework) + Status of VLC support? + Different support on different distros (Bjoern) * UX Update (Astron / Mirek) + no UX attendance * Bern Conference + book your hotels! * QA stats: + https://bugs.freedesktop.org/page.cgi?id=weekly-bug-summary.html +221-251(-30 overall) many thanks to the top bug squashers: QA Administrators 110 Maxim Monastirsky 29 Julien Nabet 9 Foss 8 Jay Philips 6 Joel Madero 5 Michael Stahl5 tommy27 5 Jean-Baptiste Faure 4 Urmas4 * Open 4.4 MAB + 4/8 4/8 3/7 3/7 2/5 1/2 1/1 + https://bugs.freedesktop.org/showdependencytree.cgi?id=79641hide_resolved=1 * Open 4.3 MAB + 14/52 14/50 11/47 14/47 14/45 19/43 10/32 6/27 5/24 5/22 3/20 26% 28% 23% 29% 33% 44% 31% 22% 20% 22% 15% + https://bugs.freedesktop.org/showdependencytree.cgi?id=75025hide_resolved=1 * Open 4.2 MAB + 83/244 83/243 84/236 85/235 82/229 81/222 76/215 74/212 74/210 71/207 34%34% 35%36%35%36%35%34%35%34% + https://bugs.freedesktop.org/showdependencytree.cgi?id=65675hide_resolved=1 * Bibisected bugs open: whiteboard 'bibsected' + 136/361 127/349 119/331 102/308 92/296 84/283 84/280 81/274 79/265 75/259 + http://bit.ly/VQfF3Q * all bugs tagged with 'regression' + 435(-4) bugs open of 2952(+8)
Re: [Libreoffice-qa] minutes of the ESC Call 2014-08-14
On Thu, Aug 14, 2014 at 06:33:37PM +0200, Bjoern Michaelsen wrote: * commit access confusion: whops, missed this link relevant to the topic and branch reviews here: https://wiki.documentfoundation.org/Development/Branches Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Minutes of ESC call: 2014-08-07
Hi Terrence, On Thu, Aug 07, 2014 at 07:30:12PM -0400, Terrence Enger wrote: I think that a publicly available VM set up for testing--especially for testing Base--would be useful, something like Drew Jensen started working on a few years ago https://wiki.documentfoundation.org/User:Drew/baseQA_VM. FWIW, I am trying to reserve some TDF funding for something along those lines right now. Money is likely the easy part of this problem, someone caring and coordinating the work to set this all up would be great. Would you maybe be interested in helping out there? Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] REPOENED Status
On Sat, Aug 02, 2014 at 10:34:01AM +0200, Florian Reisinger wrote: The bigger problem is the following: User A submitted a bug #123. A QA closes this bug as RESOLVED WFM. User A disagrees and puts the state to 1) REOPENED 2) NEEDINFO Sorry to say, but this error will continue... Well, maybe someone volunteers to watch bugs that changed state to REOPENED recently and checks if they are in the right state. Here is a query that does that for the last month: https://bugs.freedesktop.org/buglist.cgi?list_id=452344chfieldto=Nowquery_format=advancedchfield=bug_statuschfieldfrom=1mchfieldvalue=REOPENEDbug_status=REOPENEDproduct=LibreOffice returning 24 bugs moving into REOPENED, so less than ~1 bug per day. FWIW, watching this might even be a QA EasyHack, if someone wants to write and mentor that. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] REPOENED Status
On Sat, Aug 02, 2014 at 07:14:59AM -0700, Pedro wrote: I also realize that Developers prefer that Bugs should not be REOPENED because it is unlikely that the bug a user finds now is exactly the same problem that was solved before (even if the apparent result is the same and therefore the bug description is the same). They prefer that a new bug report is open. This is a major clue that REOPENED shouldn't even be visible to users... Yeah. FWIW in an ideal work with unlimited development and QA ressources it would be like this: - developer puts bug in state RESOLVED/FIXED, when this is fixed on any branch - user/QA checks the fix is working as expected and if it is, moves the bug to VERIFIED/FIXED. Otherwise, the developer is notified and the bug stays in RESOLVED/FIXED for clarification with the developer. If the developer agrees the fix is incomplete, he moves the bug back to REOPENED. - upon release of the software from the branch containing the fix, all VERIFIED bugs move to CLOSED. Only those fixes and features (which are verified and released) are advertised. Except ... we dont have the ressources for such a workflow yet (and I doubt we should fully aim for that, as it is quite a costly way to run things). OTOH some more verifying of fixes and prerelease testing wouldnt be a Bad Thing. IMHO, just regluarly watching the bugs that were recently moved to REOPENED should work well on a practical level for now though. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] 700 unconfirmed bugs milestone broke
On Sun, Jul 27, 2014 at 09:58:56PM +0200, Tommy wrote: just to say that the count is now 699 https://bugs.freedesktop.org/report.cgi?y_axis_field=bug_statusquery_format=report-tableproduct=LibreOfficeformat=tableaction=wrap great job QA team!!! Indeed, congratulations everyone! Just before release, we were back to 713. But still: we are currently at an all-time low ever since unconfirmed is the default for new bugs: https://plus.google.com/101094190333184858950/posts/XToT8Qt3WXZ Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [ANN] LibreOffice 4.2.6 RC2 test builds available
On Fri, Jul 25, 2014 at 01:26:29AM +0200, Christian Lohmaier wrote: Grab the builds from here here: http://dev-builds.libreoffice.org/pre-releases/ Users of Ubuntu 14.04 LTS also find a build in the PPAs: https://launchpad.net/~libreoffice/+archive/ppa https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-4-2 Happy testing! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] What if a bug can not be reproduced with newer version?
Hi, On Mon, Jul 21, 2014 at 02:14:52PM +0400, Aleksandr P wrote: What is current QA-team position? If you know why this bug is fixed (as in a developer said: this commit should fix that or used the bug id in a commit message) its RESOLVED/FIXED. If you cannot reproduce the bug anymore but could do so in an earlier version and you have no insight on what fixed this, its WORKSFORME. If you cant reproduce it in a current release without knowing if it was reproducable in earlier releases, use NEEDINFO or INVALID as appropriate. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] minutes of ESC call ... (2014-07-17)
* Present: Muthu, Bjoern, Eike, Mirek, Miklos, David, Norbert, Cloph, Andras, Caolan, Jacobo, Moggi, Kohei * Completed Action Items: + try to add per-process resource limits for crashtest (Markus) + eg. bash's builtin ulimit [-SHacdflmnpstuv [limit]] etc. + switch a windows tinderbox to mst-make post 4.3 (Cloph) + master tinderbox (51) does this, impressive improvement (delta 30 minutes, release build 90 minutes now) + disable the new colors of formatting marks for Mac if this causes it (Quikee) * Pending Action Items: + ask UX advise wrt. wrench icons (revert or not ?) (Astron) + blog about the sad realities of web plugins (Bjoern) + setup some VM's that can be created on-demand (Cloph) + in progress + open-source newer Synezip tests / speak at the conference (Umesh) + Ask for 1-2 more dev-list moderators re-visit next-week (Michael) + contact Michael / the list when students show up (Jan Marek) * GSOC Update (Cedric) + at least 6 students will be at the conference in Bern + a student presentation slot has been created: + thus students can prepare a 5-6 minute lightning talk on their project * Release Engineering update (Christian) + 4.2.6 status + four open changes on gerrit for libreoffice-4-2-6, rc2 next week https://gerrit.libreoffice.org/#/q/status:open+project:core+branch:libreoffice-4-2-6,n,z + 4.3.0 RC3 status + builds done + QA announce done + RC announce on libreoffice.org tonight + no open changes on gerrit for libreoffice-4-3-0 + all on track (Cloph) * Crashtest update (Markus) + crashes more frequently with 8 cores (moggi) + crash test machine reset to Mageia instead of Fedora, no reboots so far (Cloph) * Certification Committee (Stephan/Bjoern/Kendy) + waiting until ~September * Hackfests (Bjoern) + Boston Hackfest: + July 26-27th + https://wiki.documentfoundation.org/Events/2014/US_Summer_Hackfest + Tough to line-up mentoring devs + would appreciate developers via Google Hangout etc. + QA is happy to recruit programmers for our internal projects, but would like to share w/the dev team. + poke potential hosters again (Michael) + (possible) Seattle + Oct 25-27 + Straw poll: Who could make these dates? + prolly better to ping people individually (Michael) + Munich hack-fest (Jan-Marek): + will have a BSP come-together; if someone says they're coming just show up etc. + November 21st-23rd, 2014 https://wiki.debian.org/BSP/2014/11/de/Munich + we should drop by with 2 or 3 developers, if possible + Toulouse Hackfest ... + Confirmed for Nov. 15-16th + more details: https://wiki.documentfoundation.org/Hackfest/Toulouse2014 + Be great to have -really- easy easy hacks for devs (Bjoern) * 4.3 cycle Bugzilla stats (Bjoern) 4.2 4.3 Delta Change BIBISECTTOTAL 176 296 120 68.18% UNRESOLVED 60 100 40 66.67% RESOLVED 116 196 80 68.97% DUPLICATES 3725 4573 848 22.77% FIXED ALL 5320 6464 1144 21.50% ENHANCEMENTS 324 394 70 21.60% NON-ENHANCEMENTS 4996 6070 1074 21.50% enhancement fix ratio 6.12% UNCONFIRMED 790 977 187 23.67% Goal: 0% QA NEW ALL 6473 7235 762 11.77% ENHANCEMENTS 1503 1745 242 16.10% NON-ENHANCEMENTS 4970 5490 520 10.46% REGRESSIONS TOTAL2206 2837 631 28.60% UNRESOLVED349 408 59 16.91% Goal: 0% Development RESOLVED 1857 2429 572 30.80% bibisect ratio 17.19%24.51% 7.32% 42.57% Goal: 0% QA bibisect resolution ratio 13.99% of fixed regressions were bibisected this cycle
[Libreoffice-qa] Call for testing: Writer paragraph splits/joins
Hi all, I recently pushed a few canges that try to unwind one of the smaller Gordian Knots in Writer(*), to get rid of a horrible old implementation that nobody dared to touch. The new implementation isnt fancy at all (yet), but at least should pave the way for further cleaning up the code, which I plan to do as we go. For the time being however, as this is pretty low-level stuff, I ask those who are testing master/dailies to please also have a look at the behaviour of: - bookmarks - redlines (change tracking) - cursors (admittedly hardly testable in the UI) - paragraph- and character-bound objects esp. when splitting or joining a paragraph (read: insert a newline in the middle, or e.g. press backspace at the start of a paragraph. Thanks! Best, Bjoern (*) https://gerrit.libreoffice.org/gitweb?p=core.git;a=history;f=sw/source/core/doc/docbm.cxx;h=032daa849bdb282f55a1d30279f4ba464c720a34;hb=33fd0d8ae6a6b4e5226991e39fe755d84cb78280 ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [tdf-discuss] Intervention
Hi, just to quickly expand on that: On Mon, Jul 14, 2014 at 02:35:43PM +0200, Sophie wrote: I believe it is always possible for the checkers to trust the reporters and follow the steps to reproduce on their own material first; if they can't do that, they probably should ask themselves about their true motivations in this forum. I found what you say not fair for our QA members, they are doing their best to triage hundreds or reports each week. It is rare that the reporters use tricky configurations with tricky files and so on. Each way of work is different, each configuration may have their own settings depending on the company or the work. Pragmatically, if the bug is not reproducable by a QA triager (that is: someone else than the reporter), it will also not be reproducable by a developer. Without that, the bug cant be fixed really (for a fix also cannot be verified). A bug report that is not fixable is by itself unfortunately not of much value to the project. As such, we need the reporter to find a way to create a confirmed reproduction scenario. In fact, this is the small contribution (by the reporter) that helps enabling a much bigger contribution (the fix, done by a developer). With development resource being limited (they always are), they will -- all other things being equal -- naturally and effectively be used on the most well-triaged issues. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [libreoffice-projects] minutes of ESC call ...
Hi, a quick hint, since I stumbled over this: On Thu, May 08, 2014 at 04:29:41PM +0100, Michael Meeks wrote: + HackFest 'pack' / box / Virtual Machines / etc. ? + Still have hardware to try out (Bjoern) + can bring to Paris - some quadro / quad CPU thingit (TDF-owned Sun Ultra 24 with Q9650) + if we buy new hardware: something like tinderboxes we have or ... + alternatives (from ebay): + refurbished HP DL165 with 24 cores at 1.5K EUR at 1HU/15kg + refurbished Lenovo W520s at ~1K EUR each (and plane-suitable) + total cost sub Eur 5k Also note these newfangled NUCs like the ZBOX IQ01: http://www.zotac.com/products/mini-pcs/zbox/product/zbox/detail/zbox-iq01/sort/starttime/order/DESC/amount/10/section/specifications.html Intel i7-4770T, easy to transport, price currently ~600EUR with 16GB RAM. + happy to have it at his place as a tinderbox the rest of the time (Kendy) Still, the Ultra 24 we own has to go first ... Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [ANN] LibreOffice 4.3.0 rc1 test builds available
Hi, On Wed, Jun 18, 2014 at 07:28:08PM +0200, Christian Lohmaier wrote: for the upcoming new version 4.3.0 the builds for RC1 are now available on pre-releases. For testers of the upcoming Ubuntu Utopic (14.10) version, builds of this are available at: https://launchpad.net/~libreoffice/+archive/libreoffice-prereleases I hope backports to Ubuntu 14.04 LTS and Ubuntu 12.04 LTS might turn up there too at some point. This hopefully helps to get more people involved in the 4.3.0~rc1 BHS: https://wiki.documentfoundation.org/BugHunting_Session_4.3.0_RC1 Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Pushing 4.2.4 into Ubuntu Update Repo
On Fri, Jun 20, 2014 at 03:03:04AM +0400, Jay Philips wrote: I would like to suggest the addition of 4.2.4.2 into the ubuntu's trusty-updates repo as the 'Read Error' DOCX bug (fdo#77478) is still present in 4.2.3.3, which ships with Ubuntu 14.04. I assume many ubuntu and ubuntu-derivative users are going to be repeatedly submitting this same bug as time goes by, as its a major dataloss interoperability issue, as i've just encountered two such duplicates today. Please see: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/14 https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1296715/comments/17 You help in testing is appreciated. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Whiteboard Status'
Hi, a few comments: On Mon, Jun 16, 2014 at 02:39:36PM -0700, Joel Madero wrote: complextest Is this useful? If so -- when should we use it? unoapitestWe have uno is that sufficient? These are used when a complex test (like in sw/qa/complex/writer/) fails and was temporary disabled and thus need investigation/fixing. unoapitest are the same for the tests from qadevOOo. UIWe have SkillUI any reason to have it as a topic also? TopicDebugWe have SkillDebug any reason to have it as a topic also? TopicInfraWe have SkillInfra any reason to have it as a topic also? TopicWeb Component WWW? Redmine? We should keep those at least as long as we query them from the EasyHacks wiki pages. odf Suggestion to change to extension:ODF -- see previous email A prefix might make sense. extension is unfortunate though, better: filter:odf or format:odf. hfmuc2012 No clue what this is lhm-limux No clue what this is Seems Munich deployment related. We shouldnt mess with those unless they cause trouble. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] New Whiteboard Statuses
HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list Please consolidate on ONE of those before introducing this and viciously kill the others. have-backtrace looks find to me and is a registered keyword. ConfirmedCrashHalt or ConfirmedCrash ConfirmedHalt- similar to ConfirmedRegression, this would be used by the QA team to assign that they have confirmed the crash or halt of the UI, and we dont have to rely on search for random keywords to pull up an already vetted list of results IMHO, thats what Status:New vs. Status:Unconfirmed/Status:NeedInfo is for. If you find a noreproducable bug in Status:New, bump it back to NeedInfo. Id avoid double tracking this in whiteboard. WinOnly, LinOnly MacOnly - MacOnly would be very helpful to me so i can filter out the reports that i've confirmed dont happen on windows and linux, and priority can be given to these bugs by the QA team who have macs as someone already from the QA team has already confirmed its existence to be limited to mac, and also because 'Mac OS X (All)' doesn't indicate that it wont also happen on other OSes - fdo#79460 Thats what Platform:All/Win/OSX.. is for -- no need to mess up our already overloaded whiteboard with. LanguageSpecific:jp - a means of filtering reports that can only be properly tested by an individuals who know a particular language and i think it would be useful when we expand the bug submission beyond just english. - fdo#77489 Lets not be overspecific: Whiteboard status rtl should be enough -- if you find someone to actually watch those. Note the set of rtl issues seems not to be too huge: a quick query find less than 150 with RTL in subject. see also: Whiteboard status:a11y. Best, Bjoern https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard/Advanced ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] New Whiteboard Statuses
Hi, On Thu, Jun 05, 2014 at 09:06:07AM -0400, Kohei Yoshida wrote: So, to me personally, this practice of witch-hunting (or finger-pointing) really bogs me down, especially I receive such notice hundreds of times during a typical development cycle. There is no witch-hunting in this and lets please not put it in there by escalating to such vocabulary. The simple fact is that the author of a change is the one most obvious person to shed light on the issue. Having this info fast and at the right place is essential to have a good view on the state of the release and keeping everything smooth on track for train-based release schedule. Of course, if there are concrete proposals on how to improve interaction between triagers and developers that work for everyone, those are most welcome! Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Presentation Video Bug - Need Dev/QA Feedback
On Sat, May 31, 2014 at 10:46:11PM +0400, Jay Philips wrote: Yes i've had success in Xubuntu 14.04 and Linux Mint 17 after tracking down the necessary packages as mentioned in fdo#79468, as i was having problems with MKVs crashing LibO in Linux Mint 13. I did some testing on windows 7 and some formats worked (mpg, ogv, mp4, webm), while others didnt (avi, mkv). As i dont know how its being played on windows, i dont know how to remedy the issue. Note that both avi and mkv are not codecs -- they are merely containers that can contain essentially any codec, no matter how obscure: https://en.wikipedia.org/wiki/Matroska https://en.wikipedia.org/wiki/Audio_Video_Interleave For triage, it would help to know: - if an container holding one of the known working codecs works - if an container doesnt work, if the codec works outside of the container (say as mpeg4). Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice 43all bibisect (was: LibreOffice 4.3~beta1 bibisect)
HI, On Thu, May 22, 2014 at 02:27:08PM +0200, Bjoern Michaelsen wrote: On Thu, May 22, 2014 at 01:18:11AM +0200, Bjoern Michaelsen wrote: I will now merge those and upload a 43all and 43only repo replacing the current 42all and 42only ones ... 43only merged and uploaded -- so with 42all and 43only you have the range from mid-3.5 to 4.3 branchoff in two repos. Also updated to 43all now: https://wiki.documentfoundation.org/QA/HowToBibisect#Versions 755 LibreOffice builds covering 6 commits in 12GB. If 43all shows no issues soon, I will remove 42all and 42 only as obsolete soon. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Stable PPA Suggestion
On Fri, May 23, 2014 at 07:58:28PM +0400, Jay Philips wrote: Not sure if this is the best place to mention this, but i wanted to suggest that similar to having a pre-release and fresh ppa for ubuntu and derivatives, that we have a stable ppa that users who wish to stay on stable dont have to modify when a new stables comes out. Yes, Im considering that. FWIW, for the most part, the versioned ppas like: https://launchpad.net/~libreoffice/+archive/libreoffice-4-2 https://launchpad.net/~libreoffice/+archive/libreoffice-4-1 ... allow that, bot those never do a stable version bump. Then again, non-LTS releases do not see such a bump in their lifetime anyway (or only for a few weeks), thus its likely only relevant for the LTS releases anyway. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] Stable PPA Suggestion
Hi, On Fri, May 23, 2014 at 10:54:17PM +0400, Jay Philips wrote: Yes it would only be relevant to LTS users as ubuntu ships 'fresh' releases and non-LTS versions only last for 9 months. I think it could easily be achieved with a simple 301 redirect which is changed whenever a new stable is released. Has Canonical ever considered having a disabled LibO repo/ppa added by default to the repo list? Changing tooling for LibreOffice is out of question in this case. _If_ I do a stable ppa, I will just create another one and copy relevant releases to that too, just like I copy to a libreoffice-X-Y ppa. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice 43 bibisect (was: LibreOffice 4.3~beta1 bibisect)
On Thu, May 22, 2014 at 01:18:11AM +0200, Bjoern Michaelsen wrote: I will now merge those and upload a 43all and 43only repo replacing the current 42all and 42only ones ... 43only merged and uploaded -- so with 42all and 43only you have the range from mid-3.5 to 4.3 branchoff in two repos. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] 4.3 Bug Hunting Weekend!
Hi Pedro, Joel, On Thu, May 22, 2014 at 09:02:09AM -0700, Pedro wrote: jmadero wrote To download /_*latest daily build*_/ of 4.3 please go here: http://dev-builds.libreoffice.org/daily/master/ ... wouldn't it make more sense that everybody is using the same build aka the official Beta1 instead of getting a build from some random Tinderbox? I tend to agree with Pedro here. People who have done a lot of testing will have various builds anyway, but for people trying out QA for the first time, the beta1 build is likely the best thing to get started. Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice 4.3~beta1 bibisect
Hi all, On Thu, May 15, 2014 at 02:12:23PM +0200, Bjoern Michaelsen wrote: When we hit LibreOffice 4.3 branchpoint (around the beta), I plan to update again and merge the stuff into a 43all repository, but for now you should be able to do a good amount of bibisecting on master with this already. All the build are finished, but I havent merged ranges yet. Still you will find the missing 38 builds right up to the branch point in the 43beta1only repo: https://wiki.documentfoundation.org/QA/HowToBibisect#Versions This download is only 700MB -- so hardly much bigger than the usual full install, you might consider it for the upcoming bug hunting session. I will now merge those and upload a 43all and 43only repo replacing the current 42all and 42only ones ... Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
Re: [Libreoffice-qa] [libreoffice-projects] minutes of ESC call ...
Hi bfoman, On Sun, May 18, 2014 at 04:45:20AM -0700, bfoman wrote: Mozilla wants to give-away their used Mac Mini hardware for non-profit organizations. Deadline May 22nd to apply. More details at http://armenzg.blogspot.com/. If you take them, those can be turned into Mac/Linux/Windows HackFest boxes easily. Interesting. Mac minis certainly are transportable, but those are not the newest models[1] -- most Hackfest attendents will have faster hardware in their notebooks. It might be worth considering as generic tinderboxes though -- those minis are generally rather silent, so if we find some volunteers to host those, we should maybe consider to apply for 5-10 of those. Best, Bjoern [1] 2.2-2.6 Intel Core2Duo, 3MB L2 Cache is a bit slows for 1.3kg plus power supply these days .. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] LibreOffice 4.3~alpha1 bibisect
Hi all, I just uploaded an update for the Canonical LibreOffice bibisect build on Ubuntu 12.04 LTS (precise) repo for the range from LibreOffice 4.2 branchpoint to LibreOffice 4.3 alpha1 and uploaded the builds to people.canonical.com. You find link and the usual info at: https://wiki.documentfoundation.org/QA/HowToBibisect#Versions When we hit LibreOffice 4.3 branchpoint (around the beta), I plan to update again and merge the stuff into a 43all repository, but for now you should be able to do a good amount of bibisecting on master with this already. @Cloph: I seem to have lost my creds for dev-downloads.libreoffice.org again, could you mirror the file there and add those links to the wiki too? Best, Bjoern ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://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/
[Libreoffice-qa] minutes of the ESC call ...
* Present: + Kendy, Bjoern, Stephan, cloph, Lionel, Eike, Miklos, Norbert, Markus, Cedric. Eilidh, David, Michael S., Andras, Astron, Jacobo * Completed Action Items + add HackFest hardware / Amazon VMs to Board budget planning (Michael) + poke Sophie to check updating is checked in MozTrap (Cloph) + added bibisect repo (Miklos) * Dropped Action Items: + chasing build / test intermittency: + turn the SAL_WARN into a fprintf send to Cloph ? (Kendy) + run the 'make slowcheck' 20x from the top-level report (Cloph) = seems to be fixed by commits on master meanwhile + will try filing a lot of small string changes as easy hacks (Astron) * Pending Action Items: + crashtest box - more research (Moggi/Cloph) [ calc is working, writer problems can't easily be nailed down, have to use multiple processes ] [ calc numbers increased a bit - but not as bad as expected ] + encourage icon authors to put them into git (Astron) + fix the Java bridge for MSVC2012 for 4.3 (Stephan/Michael S.) + Add StarOffice OOoXML export removal to 4.2 release notes (Cloph) * Release Engineering update (Christian) + 4.3 status + failing unit tests oddness - the hunt ... + investigating Windows test failures (spellchecking) + 4.3.0 feature freeze: + next week May, 19th -- release date overlap with OSCON + take that to QA (Bjoern) + 4.2.5 RC1 - when ? + freeze in two weeks + no trouble expected + Android / iOS remote + no news + Credits: + punted until mmmeks is back http://www.libreoffice.org/about-us/credits/ + bit out of date: worth updating for 4.3 ? + 'Contributors to Bundled Templates' - oddly coloured heading. + can we separate rows better for readability ? + embolden bold name perhaps ? + tracking tags in Redmine a stupid idea? (Bjoern) * LibreOffice 4.3.0 alpha1 bibisect: + see https://wiki.documentfoundation.org/QA/HowToBibisect#Versions + 182 new builds + Cloph did some Windows bibisect builds for Florian UI stuff * 4.3 Features Page (Michael) + https://wiki.documentfoundation.org/ReleaseNotes/4.3 + please update it ! * Address Leak Sanitizer (Moggi/Sberg) + gcc/clang compiler stuff from GOOG for tracking buffer overruns etc. + works mostly out of the box + distribute build to the QA team? + runtime thing/instrumented build that spits out leaks etc. found during a run + enable for development/make check? (mst) + some junit/java trickiness here (libjpipe.so) + QA guys reporting back on bugzilla? + sure (sberg) AI: + send example (Markus) + http://lists.freedesktop.org/archives/libreoffice/2014-May/061142.html * FISL Brazil Update (Fridrich) + punted -- no Fridrich * UX update (Astron) + start menu bug updated -- not too good an idea + vendor spamming etc. + discussion at http://wordpress.com/my-stats/ + autotext stuff? * GSoC update (Fridrich/Cedric?) + where are we supposed to be at as of now ? + coding starts next week + add students with commit accounts [ for their branches ] AI: + add them to commiter group (Norbert) * Distro branches commits (Michael) punted -- no Michael * unit test documents bloating up git repo: (Michael) + might be mine (Miklos) + automated task? + test fail on too big file? + these docs are not commited with evil intend, they are sneaking in (Bjoern) + test failure on big docs might hurt local testing (Bjoern) + git-hook would prevent pushing unsuited docs though (Bjoern) + even easier (Miklos) + gerrit doesnt show how big a binary is (mst) + git hook would handle that too (Norbert) + people would evade that (Norbert) + external repo? (Norbert) + raising awareness should be enough for now (Bjoern) AI: + update git hook (Miklos) * Crashtest update (Markus) + new data ? http://dev-builds.libreoffice.org/crashtest/91821848a3a50229b8b96e91e9eb053a8ebc5d9a/ * Certification Committee (Stephan/Bjoern/Kendy) * Gerrit review request (Caolan) + lots of stuff building up there that needs review; help appreciated. + better shape than last week + we need to be more vicious on abandoning old ones AI: + walk through old changes, nag people, abandon changes (Bjoern) * Coverity Update (Caolan/Markus) + seems like a lot going on there, how are the stats ? AI: + needs a new build scheduled (moggi) * collect all bibisects at dev-downloads (Bjoern) + AFAIK e.g. Miklos has a bibisect repo somewhere + suggesting to have all bibisects with a copy at http://dev-downloads.libreoffice.org/bibisect/ too + more importantly: have all available bibisects listed at https://wiki.documentfoundation.org/Bibisect + done by now (Miklos) * C++11 for
