Re: [Libreoffice-qa] New Whiteboard Statuses
Hello all, does it make sense to include another status for the regression issues where the problematic commit has been identified ? I'm asking it because yesterday I spent some time on this task and I could chase down two regressions, one of them made by a Collabora developer ( I've already sent him an email ) and the other by a merged AOO commit. Regards, Xisco 2014-06-05 4:49 GMT+02:00 Joel Madero jmadero@gmail.com: On 06/04/2014 07:45 PM, Jay Philips wrote: Hi All, I think it might be a good idea to include the following whiteboard keywords - HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list I like all of these 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 Don't like these as much - a good bug title is sufficient to say crash IMHO and a triager can edit a title easy. 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 I think we should just use the OS field for this. Already we have way too many whiteboard status'. If we do this then OS field becomes useless and redundant. 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 +1 Best, Joel ___ 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/ ___ 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] [ANN] LibreOfficeDev 4.3.0 beta2 test builds available
Hi *, for the upcoming new version 4.3.0 the builds for Beta2 are now available on pre-releases. (some windows helppacks still uploading) It is a LibreOfficeDev build, meaning that it won't replace your stable version of LibreOffice, but can be installed alongside LibreOffice 4.2 Also note that while the build is also a key-ID build for translators, and beta1 did mark feature freeze, string and ui freeze are still to come. Significant non-code-related change for 4.3.0 is an updated build environment on Windows (Windows Server 2012R2 with Visual Studio 2012) See https://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.0_release for the complete schedule. Grab the builds from here here: http://dev-builds.libreoffice.org/pre-releases/ The list of fixed bugs relative to 4.3.0 beta1 is here: http://dev-builds.libreoffice.org/pre-releases/src/bugs-libreoffice-4-3-release-4.3.0.0.beta2-buildfix1.log So playing with the areas touched there also greatly appreciated - and validation that those bugs are really fixed. Thanks a lot for your help, Christian ___ 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] [ANNOUNCE] Tag libreoffice-4.3.0.0.beta2-buildfix1 created (on branch libreoffice-4-3)
Hi all, The tag libreoffice-4.3.0.0.beta2-buildfix1 (AKA 4.3.0 Beta2) has been created on the libreoffice-4-3 brannch. The branch will be used for fine tuning of the 4.3 codeline. See https://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.0_release for the detailed schedule of the 4.3.0 release. Master will be used for development of LibreOffice 4.4.x The following rules apply: + 4.3.0 beta phase: + any bug fixes are allowed without review + late features need approval by 3 people with different affiliation + 4.3.0 rc phase and later: + fixes need approval by one reviewer + late features need approval by 3 more people with different affiliation IMPORTANT: Every developer is responsible for pushing the fixes into all appropriate branches. Note that we do not plan any merge from this branch to master or vice versa. Please, help use to make stable and usable release. If you want to build something cool, unstable, and risky, use master. The 'libreoffice-4-2' branch is still active and will be used for the 4.2.5 bugfix release. Please read more at http://wiki.documentfoundation.org/ReleasePlan/4.2#4.2.5_release http://wiki.documentfoundation.org/Development/Branches http://wiki.documentfoundation.org/Release_Criteria Now, if you want to switch your clone to the branch, please do: ./g pull -r ./g checkout -b libreoffice-4-3 origin/libreoffice-4-3 To checkout the tag, use ./g fetch --tags ./g checkout -b tag-libreoffice-4.3.0.0.beta2-buildfix1 libreoffice-4.3.0.0.beta2-buildfix1 Hopefully it will work for you :-) Most probably, you will also want to do (if you haven't done it yet): git config --global push.default tracking When you do git push with this, git will push only the branch you are on; e.g. libreoffice-4-3 when you have switched to it. This will save you some git shouting at you. Linux distro packages might find source tarballs at http://dev-builds.libreoffice.org/pre-releases/src/ They will soon be available from the official page together with the builds. Attached is the list of changes against 4.3.0 Beta1 The -buildfix1 tag fixes a buildproblem with a failing check on windows and replaces the (not-announced and not used otherwise) tag libreoffice-4.3.0.0.beta2 Happy hacking, Christian bnc#467278 introduce a warning that changes to VBA macros cannot be saved. [Luboš Luňák, Jan Holesovsky] bnc#822625 related Cache minimum height for table cells. [Matúš Kukan] bnc#823675 (related: RTF import: get rid of hacks for \f in LISTLEVEL [Michael Stahl] bnc#863018 WW8 import: fix upper margin of multi-page floating table [Miklos Vajna] bnc#870237 wrong text position in grouped list [Zolnai Tamás] bnc#875717 handle direct formatting for numbering in .docx [Luboš Luňák] bnc#875718 discard more header/footer stuff when discarding headers/footers [Luboš Luňák] bnc#878854 MSWord uses \xb for linebreaks in DB fields [Luboš Luňák] coverity#1078626 missing break in switch [Caolán McNamara] coverity#736074 missing break in switch [Caolán McNamara] cp#172 populate cache tables when updating all external links. [Kohei Yoshida] cp#177 set 'modified' document property more consistently. [Matúš Kukan] cp#178 replace \r\n with \n when pasting from X11 clipboard. [Matúš Kukan] fdo#42899 basic: if the library is not loaded fully, copy source storage [Michael Stahl] fdo#48017 WIN32 long path support in Hyphen and MyThes [László Németh] fdo#52547 paste preference is image, then html, then text. [Andrzej Hunt] fdo#56392 fix hyphenation (remove fix, except hard hyphen part) [László Németh] fdo#59882 oops, this reference can't be const. [Matúš Kukan] fdo#62719 set more relaxed clipping region. [Jan Holesovsky] fdo#64956 editeng: fix RTF color table export [Michael Stahl] fdo#65583 elements Dock window needs scroll bar [Thomas Arnhold] fdo#67685 basic: if the library is not loaded fully, copy source storage [Michael Stahl] fdo#67935 print on group change acted as print in first group instance [Lionel Elie Mamane] fdo#67937 print on group change defaults to TRUE [Lionel Elie Mamane] fdo#68983 revert remove #if 0 block (from ... [Michael Stahl] fdo#70455 B1:SOMENAME is not a valid singleton reference [Eike Rathke] fdo#71616 related Set correct BaseSize [Thomas Arnhold] fdo#73352 don't crash if clearWarnings throws an SQLException [Lionel Elie Mamane] fdo#75971 related Crash when invoking Insert Names Create [Julien Nabet] fdo#76324 use one static SvXMLTokenMap object, it's faster. [Matúš Kukan] fdo#76752 don't add the changes toolbar to the forms window, [Markus Mohrhard] fdo#76824 proper way to parse cell address strings. [Kohei Yoshida] fdo#76953 cannot start show at selected slide [Zolnai Tamás] fdo#77206 CRASH printing with all applications on windows [Caolán McNamara] fdo#77282 replace Edit Group with Enter Group in Writer as in Draw [Laurent Balland-Poirier] fdo#77313 coinmp: error: format
Re: [Libreoffice-qa] [ANN] LibreOfficeDev 4.3.0 beta2 test builds available
Hi Christian, no Winnies: http://dev-builds.libreoffice.org/pre-releases/win/ Am 05.06.2014 11:50, schrieb Christian Lohmaier: Hi *, for the upcoming new version 4.3.0 the builds for Beta2 are now available on pre-releases. (some windows helppacks still uploading) It is a LibreOfficeDev build, meaning that it won't replace your stable version of LibreOffice, but can be installed alongside LibreOffice 4.2 Also note that while the build is also a key-ID build for translators, and beta1 did mark feature freeze, string and ui freeze are still to come. Significant non-code-related change for 4.3.0 is an updated build environment on Windows (Windows Server 2012R2 with Visual Studio 2012) See https://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.0_release for the complete schedule. Grab the builds from here here: http://dev-builds.libreoffice.org/pre-releases/ The list of fixed bugs relative to 4.3.0 beta1 is here: http://dev-builds.libreoffice.org/pre-releases/src/bugs-libreoffice-4-3-release-4.3.0.0.beta2-buildfix1.log So playing with the areas touched there also greatly appreciated - and validation that those bugs are really fixed. Thanks a lot for your help, Christian ___ 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/ -- Grüße k-j ___ 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] QA Meeting Minutes -- 2014-06-04
Hi all, Thanks for the great QA Meeting. Meeting minutes are available here: https://wiki.documentfoundation.org/QA/Meetings/2014/June_04 Our next meeting will be in two weeks on June 18th (17:30 UTC). Please feel free to add new items to the agenda here: https://wiki.documentfoundation.org/QA/Meetings/2014/June_18 Cheers, --R -- Robinson Tryon LibreOffice Community Outreach Herald Senior QA Bug Wrangler The Document Foundation qu...@libreoffice.org ___ 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] LibreOfficeDev 4.3.0 beta2 test builds available
Hi Cloph, Le 05/06/2014 11:50, Christian Lohmaier a écrit : Hi *, for the upcoming new version 4.3.0 the builds for Beta2 are now available on pre-releases. (some windows helppacks still uploading) It is a LibreOfficeDev build, meaning that it won't replace your stable version of LibreOffice, but can be installed alongside LibreOffice 4.2 Also note that while the build is also a key-ID build for translators, and beta1 did mark feature freeze, string and ui freeze are still to come. Thanks a lot :) Cheers Sophie ___ 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] LibreOfficeDev 4.3.0 beta2 test builds available
On Thu, Jun 5, 2014 at 11:56 AM, klaus-jürgen weghorn ol o...@sophia-louise.de wrote: Hi Christian, no Winnies: http://dev-builds.libreoffice.org/pre-releases/win/ uups, sorry. didn't check whether the upload was actually done when sending, just did look at the estimate when I started uploading - but in the meantime the tinderbox also decided to upload a build and did half the available upload.. :-) So eta for the windows main installer is 10-15min. ciao Christian ___ 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 Xisco, *, Xisco Faulí schreef op 5/06/2014 10:32: does it make sense to include another status for the regression issues where the problematic commit has been identified ? I'm asking it because yesterday I spent some time on this task and I could chase down two regressions, one of them made by a Collabora developer ( I've already sent him an email ) and the other by a merged AOO commit. I'm not sure about this. If you did track the bug down to a single commit (or developer), I think the keyword 'regression' + whiteboard 'bibisected' + a ping on IRC/CC or email to the particular developer is the best way. I think having the commit range, clear step-by-step actions, good summary/title and prioritizing is the most important in that case. I'm quite sure a developer who's willing to hunt down a regression will see the comment pointing towards a particular bug. Especially if you comment on it and place him/her in CC at once. Kind regards, Joren ___ 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, Jay Philips schreef op 5/06/2014 4:45: I think it might be a good idea to include the following whiteboard keywords - HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list I didn't invent it, but we have a keyword with 'have-backtrace' for this purpose. Kind regards, Joren ___ 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
On Thu, 2014-06-05 at 14:42 +0200, Joren DC wrote: Hi Xisco, *, Xisco Faulí schreef op 5/06/2014 10:32: does it make sense to include another status for the regression issues where the problematic commit has been identified ? I'm asking it because yesterday I spent some time on this task and I could chase down two regressions, one of them made by a Collabora developer ( I've already sent him an email ) and the other by a merged AOO commit. I'm not sure about this. 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. Since statistically every change one makes can and will cause *some* regressions in some obscure corners, this disadvantages those who make lots of changes, even when those changes are to fix other regressions and bugs. And some of these sometimes escalate to a (often repeated) demand of a revert of the commit, which is another blow especially when the change itself took weeks and weeks of careful coding to get conceived. One can be as careful as possible, and still (and almost always) break somethign somewhere. Kohei ___ 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] [ANNOUNCE] Tag sdremote-2.1.1 (in repository impress_remote) created
Hi all, The tag sdremote-2.1.1 (aka v11) has been created in the impress_remote repository. https://gerrit.libreoffice.org/gitweb?p=impress_remote.git;a=summary It is a minor update to the previous version that includes updated translations and action-bar buttons to turn on/off the pointer-feature. you can install the binary using playstore https://play.google.com/store/apps/details?id=org.libreoffice.impressremote or sideload it from http://downloadarchive.documentfoundation.org/libreoffice/old/sdremote-2.1.1/playstore/ A sourcetarball is available here: http://downloadarchive.documentfoundation.org/libreoffice/old/sdremote-2.1.1/src/ Happy hacking, Christian ___ 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 Kohei, Kohei Yoshida schreef op 5/06/2014 15:06: 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. Well, that's at least not what I'm talking about right now. (1) we (I) are (am) only talking about bugs we can track down to 1 single commit or developer. Not a developer in general by component (writer, calc, ...), which we do now to try to avoid as much as possible. I'm not sure that there are that many QA'ers or reporters which can track down to 1 single developer/commit? I'm not a developer at all and just to provide me an idea: do you still receive that much CC's on bugs compared to months/a year ago? (2) we discussed this yesterday on the QA-call too. Our conclusion was to just kindly ping a developer in particular on IRC. (https://wiki.documentfoundation.org/QA/Meetings/2014/June_04#Topics_for_ESC.3F) If not I still am 'pro' an active approach and mail the particular developer (in private) or put him/her in CC. (3) and as far my experience concerns... I already know which developers are and are not open for a nice (not pointing, just asking) SINGLE message. I think other core QA members do have such experience too. Since statistically every change one makes can and will cause *some* regressions in some obscure corners, this disadvantages those who make lots of changes, even when those changes are to fix other regressions and bugs. True, but luckely not all regression cases are 'obscure' and border cases. And some of these sometimes escalate to a (often repeated) demand of a revert of the commit, which is another blow especially when the change itself took weeks and weeks of careful coding to get conceived. One can be as careful as possible, and still (and almost always) break somethign somewhere. Again: true. But we are not talking about: bug the particular developer as much as possible, if he doesn't react/revert/fix spam his email and IRC with threats to revert that commit ... I think we have to find the most constructive approach to get a regression bug fixed, with respect to the situation (developer, commit message, ...) and severity. Kind regards, Joren ___ 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] Impress Remote for Android version 2.1.1 available
Hi *, A new version of the LibreOffice Impress Remote for Android has been uploaded to Google play https://play.google.com/store/apps/details?id=org.libreoffice.impressremote If you don't want to use google play (or cannot), you can sidelode the remote via http://downloadarchive.documentfoundation.org/libreoffice/old/sdremote-2.1.1/playstore/ImpressRemote.apk Besides updated translations, version 2.1.1 adds actionbar buttons to turn on/off the pointer feature of the remote. Thanks to Ahmad H. Al Harthi and all translators ( https://translations.documentfoundation.org/about/contributors/ ) for their contributions to this update. Information on participating in pre-release tests: If you are a member of the LibreOffice community on google+ ( https://plus.google.com/communities/105920160642200595669 ) you can opt-in as a tester (via https://play.google.com/apps/testing/org.libreoffice.impressremote ), in order to automatically get the updates for alpha and beta versions via google play. You can opt-out using the same URL. ciao Christian ___ 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
On Thu, 2014-06-05 at 15:41 +0200, Joren DC wrote: Hi Kohei, Kohei Yoshida schreef op 5/06/2014 15:06: 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. Well, that's at least not what I'm talking about right now. (1) we (I) are (am) only talking about bugs we can track down to 1 single commit or developer. Not a developer in general by component (writer, calc, ...), which we do now to try to avoid as much as possible. I'm not sure that there are that many QA'ers or reporters which can track down to 1 single developer/commit? I'm not a developer at all and just to provide me an idea: do you still receive that much CC's on bugs compared to months/a year ago? No because I turend off the notification. But occasional query for such bug reports turns up still quite a bit, and most of them are general Calc bugs and the reporters just add me, Eike and Markus as part of their routine bug triaging. (2) we discussed this yesterday on the QA-call too. Our conclusion was to just kindly ping a developer in particular on IRC. (https://wiki.documentfoundation.org/QA/Meetings/2014/June_04#Topics_for_ESC.3F) If not I still am 'pro' an active approach and mail the particular developer (in private) or put him/her in CC. (3) and as far my experience concerns... I already know which developers are and are not open for a nice (not pointing, just asking) SINGLE message. I think other core QA members do have such experience too. Since statistically every change one makes can and will cause *some* regressions in some obscure corners, this disadvantages those who make lots of changes, even when those changes are to fix other regressions and bugs. True, but luckely not all regression cases are 'obscure' and border cases. It's pretty subjective what a border case is. For the bug reporter, the bug he/she reported is not a border case but a serious regression that needs immediate fixing! even though others don't see it that way. And some of these sometimes escalate to a (often repeated) demand of a revert of the commit, which is another blow especially when the change itself took weeks and weeks of careful coding to get conceived. One can be as careful as possible, and still (and almost always) break somethign somewhere. Again: true. But we are not talking about: bug the particular developer as much as possible, if he doesn't react/revert/fix spam his email and IRC with threats to revert that commit ... I'm just throwing that in because it happens quite often, and is a growing concern for me. It's not targeted toward you personally. I think we have to find the most constructive approach to get a regression bug fixed, with respect to the situation (developer, commit message, ...) and severity. Sure, but please keep in mind that we currently don't have enough developers to fix all regressions, and I dare say with the current development resources (and people's (un)willingness to fix bugs), we could probably only fix 5% or less of all bugs tagged regressions. And each regression fix will (yes I'm using the word will here on purpose) create at least 2 or 3 new ones, and the cycle only continues. Maybe I'm being pessimistic, but that's how I see the situation. Kohei ___ 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] New Whiteboard Statuses
On Thu, 2014-06-05 at 16:07 +0200, Bjoern Michaelsen wrote: 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. I'm only saying how that may be peceived (and some are quite aggressive). Anyway, feel free to ignore that if you are not interested. 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. Yup, and normally the last person that touched the area gets all the pleasure of being notified of similar sounding bugs. Of course, if there are concrete proposals on how to improve interaction between triagers and developers that work for everyone, those are most welcome! No, I don't have a concrete proposal since I'm just giving my feedback. Ignore me then, and continue on. Bye, Kohei ___ 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
Hey Xisco, Hello all, does it make sense to include another status for the regression issues where the problematic commit has been identified ? I'm asking it because yesterday I spent some time on this task and I could chase down two regressions, one of them made by a Collabora developer ( I've already sent him an email ) and the other by a merged AOO commit. So in general never send a personal email to a developer unless you've been told that this is okay by the developer themselves. Our developers gets hundreds of emails per day and adding more just becomes problematic. It is sufficient to put the bibisect on the bug, say you think it might be a particular commit and if the bug is very serious (crashers/data loss) to add it to the most annoying bug list. This is sufficient to highlight the bug. Personal emails pointing fingers can irk some of our developers so best to just let them track the bug tracker the way that they see fit. All the best, Joel ___ 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 ...
* Present + Cloph, David, Eike, Fridrich, Michael M, Stephan, Thorsten, Ptyl, Miklos Kendy, Markus, Bjoern, Robinson, Michael S, Caolan, Andras, floeff, Jacobo * Completed Action Items + talk to distro vendors wrt. commit access setup (Michael) + crashtest box - more research (Moggi/Cloph) [ new control script in pure python working nicely ]. + create / promote a 4.3 MAB for WinXP/Java issues (Cloph) [ was related to python init. now fixed ] + add link on Credits page (Cloph) https://translations.documentfoundation.org/about/contributors/ + create easy hack to find an auto-abandon config/setting for a gerrit (Bjoern) https://bugs.freedesktop.org/show_bug.cgi?id=79123 + fix the Java bridge for MSVC2012 for 4.3 (Michael S.) [ done committed to -4-3 ] + teach the IRC bot. to not show distro commits (Miklos) + Tinderbox Admins: please add LibreOffice 4.3 (Thorsten co.) [ tinderboxes for all platforms rolling ]. + encourage icon authors to put icons into git (Astron) [ no response from KACST guys ... ] * Pending Action Items: * GSOC Update (Fridrich) + students should be hacking. + If there are problems with contacting, should report absence + mail reports sound positive, ~all at work. + no concerns yet. + mid-term evaluations: 23rd-27th June. + remind to ask the student to blog about what they do (Cedric) AI: + ask students to blog about it (GSOC Mentors) + steady work and progress is appreciated. * Release Engineering update (Christian) + 4.2.5 RC2 deadline is next Monday + 7x patches queued in gerrit. + 4.3.0 Beta 2 status + delays around translation, lots of problems with context, not strings themselves: now fixed. + builds currently being pushed to mirrors; for public this evening / tomorrow. + 4.3.0 UI and string freeze: week after next - branch for first RC. + Android / iOS remote + will build a new version with buttons to start/exit remote ptr. feature. + builds pushed just now for the new version; and available. + Late features ? + libreofficekit bits / rename etc. (blocking on Michael) + OpenGL pieces / status + impress work as well ? + pending GL capabilities check to avoid crashes. + experimentalising 3D chart bits. + at risk. + some changes in language listbox (Eike) + switching to a combo-box, so can enter an arbitrary lang_tag [ in: https://gerrit.libreoffice.org/9447 ] + preserving rendering OOXML Artistic Effects (Jacobo) [ in: https://gerrit.libreoffice.org/9495 ] + Calc performanc fixes (?) * Another OpenSSL issue: + https://securityblog.redhat.com/2014/06/05/openssl-mitm-ccs-injection-attack-cve-2014-0224/ + http://www.openssl.org/news/secadv_20140605.txt + awaiting patch, lower priority - release on normal 4.2.5 cadence + should we disable heartbeat completely ? (Bjoern) + we don't really need it. AI: + merge existing Fedora patches (Caolan) * allow upgrade of access2base (Lionel?) * no - Lionel, no discussion / decision. + access2base now included in LibreOffice 4.2 and later + technical structure: one Basic library (and that's it) + for other branches (other forks of OO.org LibreOffice 4.1 and earlier), available as extension + competitive disadvantage: users of other branches can have newer access2base faster (install extension) + not possible for LibO 4.2 later because extension not allowed to override part of LibreOffice (only other extension) + policy exception for access2base can have new features within stable line? + I don't like that + allow extensions to override any part of LibreOffice? + no, significant resistance + allow extensions to override any *script* or *dialog* library from LibreOffice? + allow extensions to override any *Basic* or *dialog* library from LibreOffice? + allow extensions to override any *Basic* (not *dialog*) library from LibreOffice? + rationale: AFAIK, we don't ship any wizard / conversion / ... code as Basic, only examples + needs to be validated by domain expert + allow extensions to override only access2base? + demote access2base to bundled extension? + makes Acces2Base much less official in LibreOffice :-( (also more work) * UX Update (Astron) + a few UX advise bugs getting discussed. + colour of non-printing characters ... + customizable or not ? * Crashtest update (Markus) + new result including writer/impress/draw http://dev-builds.libreoffice.org/crashtest/7c8b2f10310f0f64b111afb3012e82e9c4a690ac/ +
Re: [Libreoffice-qa] New Whiteboard Statuses
On 06/05/2014 05:36 AM, Joren DC wrote: Hi, Jay Philips schreef op 5/06/2014 4:45: I think it might be a good idea to include the following whiteboard keywords - HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list I didn't invent it, but we have a keyword with 'have-backtrace' for this purpose. Ah I didn't see that. We should change it to camel case to be consistent. HaveBacktrace. Will include on whiteboard page. Best, Joel ___ 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
Crap I see ;) Thanks - we can talk about consistency between keyword and whiteboard once we actually get our own instance of bugzilla :) Best, Joel On 06/05/2014 08:29 AM, Joren DC wrote: Joel Madero schreef op 5/06/2014 17:26: Ah I didn't see that. We should change it to camel case to be consistent. HaveBacktrace. Will include on whiteboard page. Just to be sure: have-backtrace is a keyword and our key words are not camel-cased ;-). We may want to consider to make it more consistent if we have our own bugzilla instance :-)? Cheers, Joren ___ 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/ ___ 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
On 06/05/2014 05:36 AM, Joren DC wrote: Hi, Jay Philips schreef op 5/06/2014 4:45: I think it might be a good idea to include the following whiteboard keywords - HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list I didn't invent it, but we have a keyword with 'have-backtrace' for this purpose. Nevermind - this is a keyword not a whiteboard status so it is indeed have-backtrace which applies to debug, backtrace, strace :) Best, Joel ___ 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
Joel Madero schreef op 5/06/2014 17:26: Ah I didn't see that. We should change it to camel case to be consistent. HaveBacktrace. Will include on whiteboard page. Just to be sure: have-backtrace is a keyword and our key words are not camel-cased ;-). We may want to consider to make it more consistent if we have our own bugzilla instance :-)? Cheers, Joren ___ 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 Joren, Looking over keywords, you are correct that it has 'have-backtrace', it even has 'want-backtrace', and it also has keywords that arent that useful in the keyword field like bibisected (used in WhiteBoard), NEEDINFO (used in status), and notourbug (used in status). Regards, Jay Philips On 06/05/2014 04:36 PM, Joren DC wrote: Hi, Jay Philips schreef op 5/06/2014 4:45: I think it might be a good idea to include the following whiteboard keywords - HasDebug or HasBacktrace HasStrace - When the bug reporter or commenter has included the backtrace or strace output, so devs can easily see this list I didn't invent it, but we have a keyword with 'have-backtrace' for this purpose. Kind regards, Joren ___ 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/ ___ 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] Bug Reporter Wants To Submit Patch
Hi All, The bug reporter of 79599 has done all the ground work and would like to submit some code, so if someone from the devs could nudge him in the right direction. -- Regards, Jay Philips ___ 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] RE LibreOffice
Hi Brian, Sorry for the long delay - not sure if someone else already responded. Chrome is giving a false positive - it's a bug on there side. You can force the download (or download using a different browser) and everything will work fine. Best, Joel P.S. Thanks so much for the donation - is not a requirement to use LibreOffice but it is definitely appreciated and helps us continue to grow our fantastic product. On 05/09/2014 10:36 AM, Quizman wrote: Yes, I wish to subscribe and have given a donation via PayPal. However, when downloaded, Chrome, my web browser has BLOCKED the download stating this is malicious software. Please advise. Kind regards Brian Crane (Quizman) My eBook Confessions of a Quiz Show Writer available at: http://www.amazon.co.uk/Confessions-Quiz-Show-Writer-ebook/dp/B007RD4SXS Also see my BLOG: http://quizsupplies.blogspot.co.uk/ ___ 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/ ___ 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] Backtrace on Linux
On Thu, Jun 5, 2014 at 6:36 PM, Jay Philips philip...@hotmail.com wrote: Hi All, I submitted my first windows and linux backtraces today to fdo#79569, and would love feedback on it so i know i've done it right. On the linux site, i noticed that when i run 'soffice --backtrace', one of the lines that it outputs is Reading symbols from /opt/libreoffice4.2/program/soffice.bin...(no debugging symbols found)...done. which makes me think i'm missing something. So are all linux installations from the .tar.gz files found on the website and in the daily builds, debug enabled? I believe that all of our regular tarballs are unstripped, yes. Did you install a TDF build to /opt, or is that a distro-supplied build? Cheers, --R --- Robinson Tryon LibreOffice Community Outreach Herald Senior QA Bug Wrangler The Document Foundation qu...@libreoffice.org ___ 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] Bug Reporter Wants To Submit Patch
On Thu, Jun 5, 2014 at 7:08 PM, Jay Philips philip...@hotmail.com wrote: Hi All, The bug reporter of 79599 has done all the ground work and would like to submit some code, so if someone from the devs could nudge him in the right direction. Hi Jay, The more programmers, the merrier! I'd point anyone interested in submitting patches here: https://www.libreoffice.org/community/developers/ and here: https://wiki.documentfoundation.org/Development/How_to_build Don't forget to mention the #libreoffice-dev channel on Freenode. Communication is key! Best, --R -- Robinson Tryon LibreOffice Community Outreach Herald Senior QA Bug Wrangler The Document Foundation qu...@libreoffice.org ___ 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/
