RE: Can we add the value "N/A" to the Target Milestone field

2016-03-21 Thread Dennis E. Hamilton
> -Original Message- > From: Pedro Lino [mailto:pedl...@gmail.com] > Sent: Monday, March 21, 2016 16:53 > To: qa@openoffice.apache.org > Subject: Re: Can we add the value "N/A" to the Target Milestone field > > > It's not about to draw the line between issues that are resolved and > >

Re: Can we add the value "N/A" to the Target Milestone field

2016-03-21 Thread Pedro Lino
> It's not about to draw the line between issues that are resolved and > verified solutions. It's about to differentiate issues that are in the real > application and therefore need to be fixed in the source code. Here we use > (or better should use) RESOLVED - FIXED. > > But what about issues

Re: Can we add the value "N/A" to the Target Milestone field

2016-03-21 Thread Pedro Lino
On Mon, Mar 21, 2016 at 10:32 PM, Marcus wrote: > Am 03/21/2016 10:36 PM, schrieb Kay Schenk: > >> [top posting] >> >> Thanks for all the help with this and for the new NONE for >> target release. Hopefully, it will be used sparingly >> assuming we us e RESOLVED-FIXED as

Re: Can we add the value "N/A" to the Target Milestone field

2016-03-21 Thread Kay Schenk
[top posting] Thanks for all the help with this and for the new NONE for target release. Hopefully, it will be used sparingly assuming we us e RESOLVED-FIXED as only for issues in which an actual commit is used. Issue 126828 has now been changed to UNCONFIRMED. How to differentiate UNCONFIRMED

Fwd: Can we add the value "N/A" to the Target Milestone field

2016-03-21 Thread Kay Schenk
Forgot to copy qa on my reply. -- Forwarded message -- From: Kay Schenk Date: Mon, Mar 21, 2016 at 8:59 AM Subject: Re: Can we add the value "N/A" to the Target Milestone field To: OOo Apache , Dennis Hamilton <