[libreoffice-projects] Re: 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 -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] [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 -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] [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 -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Re: [Libreoffice-qa] QA Meeting Minutes - 2014-12-03
On Mon, Dec 8, 2014 at 3:43 PM, Tommy ba...@quipo.it 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 -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
