Re: [Libreoffice-qa] QA Meeting Minutes - 2014-12-03
On Tue, 09 Dec 2014 05:29:23 +0100, Robinson Tryon wrote: How do we decide which bugs to tag? I suggest that for now we only tag backportRequests if the bug was reported against an active Still or Fresh branch. So to put that into context with our current builds, here's my proposal: If you test a bug reported against 4.3 and find 1) It's fixed in master, AND 2) It's not fixed in 4.3.5.1 (the latest build on the 4.3 branch) Then change status -> WFM, and add "bibisectRequest backportRequest" to the Whiteboard. I think this is the easiest and more practical solution. we should also alert the most active bibisecter that their job in these bugs is different... they usually look for the version were the bug appears first, this time where the bug is finally gone. it's kind of reverse bibisecting... that program was ideated to find bugs but you can also use it to find fixes. For all other cases, if it's fixed in master, then (just) change status -> WFM. Best, --R ___ 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] QA Meeting Minutes - 2014-12-03
On Mon, Dec 8, 2014 at 3:43 PM, Tommy wrote: > if we don't mark it as FIXED WFM how do we distinguish a NEW bug without a > fix from a NEW bug which is FIXED in master but not yet present in the > stable branch? Sure -- and this highlights a granularity problem we have with current bug reports: We only have a binary switch to indicate if a bug has been fixed or not. We currently use the Version field to point to the oldest LO version on which we can reproduce a bug. If we had a 2nd Version field, we could use that to point to the newest LO version on which we can reproduce, but IMHO that's still not as granular as I'd like. I've some cursory ideas for how we can more clearly indicate which environments (LO version + OS + etc..) reproduce a given bug, which we can revisit after the Bugzilla Migration. > I think the scenario Robinson depicted is logical. > > 1- QA finds that a NEW bug in stable branch is somehow fixed in master so it > marks it as WFM > > 2- a bibisect attempt is done to identify the committ that fixed it > > 3- once the bibisect is done, a backportRequest is added to whiteboard and > devs are contacted While we do have other work in the QA task pool (triaging incoming bugs, bibisecting open regressions, etc..), let's see how many fixed bugs get tagged with bibisectRequest, and see how quickly we're able to address them. If the number is small, it shouldn't represent much of an additional burden for QA. If we just tag a bug with bibisectRequest and resolve it as WFM, I think bibisecters might ignore it, so I suggest that we tag it bibisectRequest + backportRequest at the same time. To help us keep track of these bugs, I've added two entries to the Useful Queries page: https://wiki.documentfoundation.org/QA/Bugzilla/Useful_Queries#Common_Lists_of_Bugs 1) Backport requests that need bibisection 2) Backport requests that do not need bibisection (i.e. needs dev attention) How do we decide which bugs to tag? I suggest that for now we only tag backportRequests if the bug was reported against an active Still or Fresh branch. So to put that into context with our current builds, here's my proposal: If you test a bug reported against 4.3 and find 1) It's fixed in master, AND 2) It's not fixed in 4.3.5.1 (the latest build on the 4.3 branch) Then change status -> WFM, and add "bibisectRequest backportRequest" to the Whiteboard. For all other cases, if it's fixed in master, then (just) change status -> WFM. Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald 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/
[Libreoffice-qa] [ANN] LIbreOffice 4.2.8 RC2 available
Dear Community, The Document Foundation is pleased to announce the second release candidate of LibreOffice 4.2.8. The upcoming 4.2.8 is an additional bugfix release to finish off the 4.2 codeline line. Feel free to give it a try instead of 4.2.7. The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Developers and QA might also be interested in the symbol server for windows debug information (see the release notes linked below for details) Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.freedesktop.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.2.8 RC2 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.2.8/RC2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. On behalf of the Community, 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] [ANN] LibreOffice 4.4.0 Beta2 available
Dear Community, The Document Foundation is pleased to announce the second Beta release of LibreOffice 4.4.0. The upcoming 4.4.0 will be the ninth major release of LibreOffice, coming with a bunch of new features beside the usual bugfixes. The Beta2 can be installed alongside the stable version, so feel free to give it a try. Beta2 is not ready for production yet, and while Beta1 marks feature freeze, final UI and string freeze is yet to come, and translations are not complete. A work-in-progress list of new features in LibreOffice 4.4 can be found at https://wiki.documentfoundation.org/ReleaseNotes/4.4 The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases Developers and QA might also be interested in the symbol server for windows debug information (see the release notes linked below for details) Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.freedesktop.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.4.0 Beta2 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.4.0/Beta2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. On behalf of the Community, 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] time to remove all 4.1.x RC versions
Hey Tommy, Any FDO cleanup - if you cc me on it I'll address the issue. Only a few people have rights as of now. > >> > I see that somebody did the clean up but forgot to remove just the > 4.1.6.1 rc Resolved :) Thanks! 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] mab4.2 to mab4.3 migration almost over
On Mon, 08 Dec 2014 11:52:59 +0100, Tommy wrote: here's the list of the last mab4.2 "survivors": https://bugs.freedesktop.org/showdependencytree.cgi?id=65675&hide_resolved=1 good to see that we were able to reduce the number to just 5: 54398: FILESAVE: DOC files created in LO lose drawings (anchored as character probably - and grouped?) after field update in MS Word 2007 54933: EDITING Report builder: mouse-move control: gap between mouse position 59613: RTL VIEWING: Increasing size of dialogs to right or bottom causes artifacts 72504: EDITING: Unable to edit .odb file with non-local URL 81056: docx export of ducks beaks MS Import ... let's get rid of this "handful of MABs" :-) ___ 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] QA Meeting Minutes - 2014-12-03
On Mon, 08 Dec 2014 13:38:58 +0100, Eike Rathke wrote: Hi, On Saturday, 2014-12-06 21:18:05 -0500, Robinson Tryon wrote: * If a bug is fixed on the Master branch (or in Fresh), but is still present on Fresh/Still, it can be helpful to tag the bug and bibisect it, in addition to resolving it as WFM. I'll send out a separate email to the QA list with some advice from the devs. IMHO a bug should not be resolved as WFM then, it is still a bug in the release reported. If it is fixed in master then even better, hopefully it was one commit that can be cherry-picked, so a bibisect indeed would be welcomed. Eike I respectfully disagree with you Eike. we have to mark it FIXED WFM anyway as soon as it gets fixed in master. we don't have to wait for backport before declaring it fixed... if we don't mark it as FIXED WFM how do we distinguish a NEW bug without a fix from a NEW bug which is FIXED in master but not yet present in the stable branch? I think the scenario Robinson depicted is logical. 1- QA finds that a NEW bug in stable branch is somehow fixed in master so it marks it as WFM 2- a bibisect attempt is done to identify the committ that fixed it 3- once the bibisect is done, a backportRequest is added to whiteboard and devs are contacted 4- devs decide wheter to backport or not the fix, if it's technically feasible or not 5- if backport is possible the fix goes into the stable branch and we may set status CLOSED 6- if backport is not possible we put whiteboard "backportDenied" and wait till the release of the first .0 release of the master branch before declaring it closed anyway, considering the fast release cycle of LibO, the waiting time needed before master turns into a .0 release is acceptable for most of our users... I have some pet bugs that I know were fixed in summer in the 4.4 master but not backported into 4.3.x and I'm waiting patiently without any drama for february 2015 when the 4.4.0 final release will come out. please guys, let's all remind the OOo times when people had to wait years before seeing patches into a final release... LibO is doing a better job with this ___ 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] libreoffice-4.4.0.0.beta2 (on branch libreoffice-4-4) created
Hi all, The tag libreoffice-4.4.0.0.beta2 (AKA 4.4.0 Beta2) on the corresponding branch libreoffice-4-4 has been created last week. The branch will be used for fine tuning of the 4.4 codeline. Branch-off marks feature freeze, see https://wiki.documentfoundation.org/ReleasePlan/4.4#4.4.0_release for the detailed schedule of the 4.4.0 release. Master will be used for development of LibreOffice 4.5.x The following rules apply: + 4.4.0 beta phase: + any bug fixes are allowed without review + late features need approval by 3 people with different affiliation + 4.4.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-3' branch is still active and will be used for the 4.3.6 bugfix release. Please read more at http://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.6_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-4 origin/libreoffice-4-4 To checkout the tag, use ./g fetch --tags ./g checkout -b tag-libreoffice-4.4.0.0.beta2 libreoffice-4.4.0.0.beta2 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-4 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.4.0 Beta1 Happy hacking, Christian + the assert seems to just want the attrs to be sorted (bnc#467459) [Caolán McNamara] + wrong background color shown in format table in impress (bnc#882627) [Caolán McNamara] + text(box) is rendered white on white when it is not (bnc#904423) [Zolnai Tamás] + unchecked return value (cid#1255906) [Tor Lillqvist] + busted loop condition and Resource leak (coverity#1255390) [Caolán McNamara] + buffer not null terminated (coverity#1255905) [Caolán McNamara] + explicit null dereferenced (coverity#1255907) [Caolán McNamara] + uninitialized scalar field (coverity#1255909) [Caolán McNamara] + uninitialized scalar field (coverity#1255910) [Caolán McNamara] + fix SQL view to be editable (coverity#706316) [Caolán McNamara] + revert "Logically dead code" (coverity#735424) [Lionel Elie Mamane] + mirror fixes for and into icu (deb#766788) [Caolán McNamara] + avoid empty style names in ww2 docs (fdo#36514) [Caolán McNamara] + go back to the old way of doing things (fdo#48846) [Caolán McNamara] + reintroduce embedded picture for form components (fdo#53001) [Lionel Elie Mamane] + don't call XLSX methods in XLS export, related (fdo#59762) [Markus Mohrhard] + reintroduce embedded picture for form components (fdo#65163) [Lionel Elie Mamane] + export more numbering types correctly into HTML (fdo#68684) [Andras Timar] + fix crash on loading (fdo#70157) [Caolán McNamara] + cui: fix crash in SvxExtParagraphTabPage (fdo#70861) [Michael Stahl] + RTF import: bogus call to getBestTextEncodingFromLocale() (fdo#72031) [Miklos Vajna] + improving on existing icons and adding entries into links.txt (fdo#75256) [Matthias Freund, Yousuf Philips] + go back to the old way of doing things (fdo#75408) [Caolán McNamara] + check internal and external sheet references in both modes (fdo#77018) [Eike Rathke] + related: only make outline, title and subtitle read-only (fdo#78151) [Caolán McNamara] + mirror fixes for and into icu (fdo#78906) [Caolán McNamara] + accept args for .uno:InsertAnnotation (fdo#78980) [Maxim Monastirsky] + revert "SwToSfxPageDescAttr: fix call to ... (fdo#79303) [Michael Stahl] + fix again and keep references to other sheets during sort (fdo#79441) [Eike Rathke] + duplicate acceserator keys in spell checking dialog (fdo#79707) [Caolán McNamara] + make sure to check for formula first, (fdo#80301) [Julien Nabet] + fix SQL view to be editable (fdo#80938) [Caolán McNamara] + removal of font name, font size and text alignment from context menus (fdo#81132) [Yousuf Philips] + rearrange, add and remove entries from toolbars (fdo#81475) [Yousuf Philips, Maxim Monastirsky] + RTF filter: import \sbauto and \saauto (fdo
Re: [Libreoffice-qa] QA Meeting Minutes - 2014-12-03
Hi, On Saturday, 2014-12-06 21:18:05 -0500, Robinson Tryon wrote: > * If a bug is fixed on the Master branch (or in Fresh), but is still > present on Fresh/Still, it can be helpful to tag the bug and bibisect > it, in addition to resolving it as WFM. I'll send out a separate email > to the QA list with some advice from the devs. IMHO a bug should not be resolved as WFM then, it is still a bug in the release reported. If it is fixed in master then even better, hopefully it was one commit that can be cherry-picked, so a bibisect indeed would be welcomed. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack pgpLrRnNtMyS_.pgp Description: PGP signature ___ 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
On Mon, 08 Dec 2014 11:45:59 +0100, Tommy wrote: hi guys, I've retested and migrated most of the mab4.2 to the mab4.3 list. of the original 83 mab4.2 issue that were still open on the 4.2.x END OF LIFE (november 19th) a few were marked as RESOLVED WORKSFORME see list here: https://bugs.freedesktop.org/show_bug.cgi?id=65675#c235 I have still 13 mab4.2 that I'm not able to retest (most of them are Linux or MacOS specific issues) so please I ask the help of other QA members to finish the job. here's the list of the last mab4.2 "survivors": https://bugs.freedesktop.org/showdependencytree.cgi?id=65675&hide_resolved=1 ___ 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
On Mon, 08 Dec 2014 11:45:59 +0100, Tommy wrote: hi guys, I've retested and migrated most of the mab4.2 to the mab4.3 list. of the original 83 mab4.2 issue that were still open on the 4.2.x END OF LIFE (november 19th) a few were marked as RESOLVED WORKSFORME see list here: https://bugs.freedesktop.org/show_bug.cgi?id=65675#c235 I have still 13 mab4.2 that I'm not able to retest (most of them are Linux or MacOS specific issues) so please I ask the help of other QA members to finish the job. here's the list of the last mab4.2 "survivors": https://bugs.freedesktop.org/showdependencytree.cgi?id=65675&hide_resolved=1 ___ 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] mab4.2 to mab4.3 migration almost over
hi guys, I've retested and migrated most of the mab4.2 to the mab4.3 list. m -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ 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/
