Re: [Libreoffice-qa] Keyword for ux-advise

> Kendy felt it maybe difficult and wanted to know if it was possible to > do this from the bugzilla end so that it would be automatic. Probably easier solution is that 2 or 3 of you just monitor this link routinely (has keyword, does not have UX in mailing list):

Re: [Libreoffice-qa] NEW Ping latest run

On 04/16/2016 12:44 AM, Tommy wrote: > hi there, just a few minutes ago I did a new run of the NEW BUGS > UNTOUCHED FROM MORE THAN 1 YEAR ping. Thanks Tommy! I will *try* to write a blog post with a couple pretty graphs/charts in about 3 weeksno promises, life is pretty hectic right now. If

Re: [Libreoffice-qa] Keyword for ux-advise

On 04/17/2016 02:11 PM, Yousuf 'Jay' Philips wrote: > maybe difficult and wanted to know if it was possible to > do this from the bugzilla end so that it would be automatic. Not by default - it would require some hacking of bugzilla. ___ List Name:

Re: [Libreoffice-qa] Keyword for ux-advise

Hey, On 04/17/2016 08:53 PM, Joel Madero wrote: Hi, The design team would like a 'needsUXEval' keyword added to the keywords field, so that ux-advise bugs can be assigned that keyword instead of having ux-advise assigned in the component field, so for example it would be easy to search bugs

Re: [Libreoffice-qa] Keyword for ux-advise

On 04/17/2016 08:13 AM, Yousuf 'Jay' Philips wrote: > Hi All, > > The design team would like a 'needsUXEval' keyword added to the > keywords field, so that ux-advise bugs can be assigned that keyword > instead of having ux-advise assigned in the component field, so for > example it would be easy

Re: [Libreoffice-qa] Check for update

Hi Pedro, *, On Sun, Apr 17, 2016 at 6:06 PM, Pedro wrote: > Hi all > > While checking if bug #46354 was fixed I found an odd result > > If I use version > > Version: 5.1.2.1 (x64) > Build ID: 2603b69c5ec5981bb5f053f8ebfd1f3de00a4c29 > […] > and Check for Updates, I get

Re: [Libreoffice-qa] Keyword for ux-advise

Hi, > The design team would like a 'needsUXEval' keyword added to the > keywords field, so that ux-advise bugs can be assigned that keyword > instead of having ux-advise assigned in the component field, so for > example it would be easy to search bugs in Draw that require ux-advise. Done > > QA

[Libreoffice-qa] Check for update

Hi all While checking if bug #46354 was fixed I found an odd result If I use version Version: 5.1.2.1 (x64) Build ID: 2603b69c5ec5981bb5f053f8ebfd1f3de00a4c29 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: pt-PT (en_US) and Check for Updates, I get "LibreOffice 5.1 is up to

[Libreoffice-qa] Keyword for ux-advise

Hi All, The design team would like a 'needsUXEval' keyword added to the keywords field, so that ux-advise bugs can be assigned that keyword instead of having ux-advise assigned in the component field, so for example it would be easy to search bugs in Draw that require ux-advise. QA members

Re: [Libreoffice-qa] writing unit test for calc functions

On 16.4.2016 12:20, Markus Mohrhard wrote: @QA team: Does this sound like something that would make it easier for you to add tests for spreadsheet functions? Hi Markus, both variants are similarly arduous, so it's developer decision. If these new test will lead to easier incorporating of