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



What is the workflow if I see a bug report that might be easy enough to be an easy hack, but I 
have
zero knowledge about the underlying code? My ability to evaluate it stops before the first action 
step
detailed in response to Problem 4. So, CC Jan and ask his opinion? Does any keyword need to be 
set?


Whenever somebody sets keyword=easyhack I get a message next morning, so need for a keyword in that 
case. No need to put me CC.

I control all easyhack and currently set status=NEEDINFO if information is missing. I agree that 
using keyword=needsDevEval instead would make more sense.

rgds
jan I.

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.