Pending Action Items

+Triaging NEEDINFO
-AGREED: We will move forward with auto closing these bugs moving into the future
-AGREED: One warning will be given where we:

Thanks users for their report

Acknowledge that it's been in NEEDINFO for at least 180 days

Ask again for information requested

Say that if information is not given within 1 month, bug will be auto closed as INVALID

-ACTION: Florian will write text for first “warning”
-General agreement that at most it would be 20% of bugs are actual bugs but more likely much lower than this and without this move, they would never be touched

New Action Items

NEW ITEM: FreeDesktop.Org

Triagers will try their best to add comments when they add a bug to MAB

UNCONFIRMED – remove them

NEEDINFO – can stay on there, but shouldn't stay on NEEDINFO

+QA Field
-We've been much better about assigning ourselves as QA contact after triaging
-Action: Joel will contact Tollef about getting a “take” option for QA field

NEW ITEM: Hard Hacks

+New bugs added, awaiting feedback from developers
+Candidates should be limited to MAB list for the most part but other particularly difficult/annoying bugs can be added

NEW ITEM: QA Project / Realistic Goal

+ACTION: Joel will work on getting this page started, should include all projects (long/short) along with goals and “lead contacts”

NEW ITEM: Timestamp for Master Builds

+Action: Petr will look into getting some kind of time stamp in the about section of master builds, latest commit date/time is best but other option is time of build.
+Bjoern may know something about this as there was discussion a year+ ago about doing this

NEW ITEM: New Features

+Major concern about new features squeezing through without enough QA testing
+Many times QA is unaware of new features until it's too late to test, no good list to “test first”
+Action: Joel will ask ESC if they are okay with
-Developers create or use an existing bug and add "feature:<version>" flag into whiteboard, e.g "feature:4.1"
*This will help to find a tested even during the development phase
-Developers mention new feature in the release notes once completed; see links at ReleasePlan ;

mention there the existing bug if exists;

the bugs has to me marked as FIXED

+QA monitor the release notes page; They make sure that all features have assigned bug and that all bugs have the proper "feature:<version>" flag; It the bug does not exist, they create it and add the developer into CC; the bugs should be marked as FIXED at this stage because the feature is ready
+ the bug will be used to track the testing activity and marked as verified once it pass testing; it could be used as a meta bug for tracking related bugs that breaks using the feature

+Agreed: QA will use “verified” more frequently with FIXED Enhancements especially those marked as NewFeature
+Agreed: Comments will be used to show that multiple QA people test new features
+Petr brought up moztrap being a possibility to test new features

-Needs further investigation (volunteers needed)

NEW ITEM: Talkyoo Broken (skype)

+ACTION: Petr will look into other options as this call two people tried calling in using skype but failed to successfully connect

+Joel
-Metrics (bugs)
-Update QA and QA-Team Wiki
-Bug Importance/Priority Default
-E-Mail QA-Team page members to find out if they want to remain on list
-Ping Tollef to see if we can make it so NEEDINFO and WFM bugs can go back to UNCONFIRMED bugs
-Shipping options for prizes/gifts

Tools

Please note that all contributions to The Document Foundation Wiki are considered to be released under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported License], unless otherwise specified. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ([http://www.libreoffice.org/download/license/ LGPLv3]). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our [[TradeMark Policy|trademark policy]] (see [[Project:Copyrights]] for details). LibreOffice was based on OpenOffice.org.If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.