Forgot to copy qa on my reply. ---------- Forwarded message ---------- From: Kay Schenk <kay.sch...@gmail.com> 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 <d...@openoffice.apache.org>, Dennis Hamilton < dennis.hamil...@acm.org>
On Sun, Mar 20, 2016 at 3:46 PM, Dennis E. Hamilton <dennis.hamil...@acm.org > wrote: > I want to clarify this. > > I think the problem might be that "Resolved - Fixed" is being used > incorrectly. As far as I know, there are many cases where this resolution > is used where one of "Resolved - Not an Issue" (though not too often), > "Resolved - Irreproducible", "Resolved - Won't Fix", or "Resolved - > Obsolete" should be used. > > Is that what you are seeing, Kay? > Well maybe so. In the past, I have used RESOLVED-FIXED to determine what's been committed to our source, thus leading to a Target Release. Yesterday, I started going through RESOLVED-FIXED items to be sure some of these fixed issued did have a Target Release. Some of these RESOLVED-FIXED issues seem to be either user support issues/questions that do not entail source code corrections at all, or similar type situations. In one of the cases I sited above, I think the issue originator marked it with RESOLVED-FIXED, and really i don't know if this was the right thing to do or not. So, we can use the new NONE (thank you Marcus!) as the Target Release, or do something else to ignore these types of issues for verification in a build. The problem is stemming from the use of BZ as both a code centric problem reporting mechanism and a user support tool. > > In those cases, it is preferable to change the resolution. > > > -----Original Message----- > > From: Andrea Pescetti [mailto:pesce...@apache.org] > > Sent: Sunday, March 20, 2016 14:09 > > To: qa@openoffice.apache.org; d...@openoffice.apache.org > > Subject: Re: Can we add the value "N/A" to the Target Milestone field > > > > Kay Schenk wrote: > > > We seem to have a number of issues in BZ that are now listed > > > as Resolved/Fixed but don't seem to pertain to an actual > > > upcoming release. > > > > Everything that was marked RESOLVED FIXED will be in 4.2.0. So 4.2.0 is > > a perfectly valid value for these cases. > > > > Just to be clear: 4.1.2 was a maintenance release and issues had to be > > approved as release blockers in that case. 4.2.0 will be a normal > > release, made from trunk, so everything that is on trunk (untile a > > certain moment when we will decide to branch) will be into it > > automatically. So the target is 4.2.0 in those cases. > > > > Regards, > > Andrea. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: qa-h...@openoffice.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- ---------------------------------------------------------------------- MzK "Time spent with cats is never wasted." -- Sigmund Freud -- ---------------------------------------------------------------------- MzK "Time spent with cats is never wasted." -- Sigmund Freud
