Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi All,

I think this is the easiest way to keep track of bugs that QA thinks easy
hack is appropriate but that we don't have the programming skills to direct
users to appropriate code or assign a developer to "mentor" the bug fixer
as they try to tackle these easy hacks. This will help us move more bugs
into easy hack status but requires both QA and developers to keep track of
the list. Looking for feedback


http://wiki.documentfoundation.org/Development/Easy_Hacks#New_EasyHacks.2C_Developer_Input_Required

Regards,
Joel

-- 
*Joel Madero*
LibO QA Volunteer
jmadero.dev@gmail.com

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "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.