openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Marcum <>
Subject Re: Can we add the value "N/A" to the Target Milestone field
Date Mon, 21 Mar 2016 22:30:26 GMT
On 03/21/2016 03:05 PM, Dennis E. Hamilton wrote:
>> -----Original Message-----
>> From: Keith N. McKenna []
>> Sent: Monday, March 21, 2016 10:22
>> To:
>> Subject: Re: Can we add the value "N/A" to the Target Milestone field
>> Kay Schenk wrote:
> [ ... ]
>>> The problem is stemming from the use of BZ as both a code centric
>> problem
>>> reporting mechanism and a user support tool.
>> You are right on that. Historically Bugzilla was used strictly to track
>> items that were issues with the OpenOffice software itself, and not for
>> use as a user support venue. That is why we had and still have the
>> support forums and the user mailing list. IMHO it is perfectly correct
>> to to use Resolved-Not An Issue to close purely support issues.
>> Keith
> [orcmid]
> I have already remarked that I think this separation is too binary.  These are often
not "purely support" matters and the mailing lists are often not that helpful.  The forums
are great when an issue is curated so that users don't have to parse all the comments to figure
out what's-what.
> One thing the BZ does, if someone has figured out how to make a report, is provide issue-specific
mailings of comments back to the reporter, and that's automatic.
> Also, my view is that every BZ issue (and reports on lists and the forums) is a gift.
 Someone went to a fair amount of difficulty to make their experience known.  We should be
grateful and that should be reflected in responses.  Users are completely baffled by "NOT
AN ISSUE" when that is patently untrue in their world and I doubt it reflects well on the
> Sometimes users, based on provided comments, will figure out that it may be something
they did and can avoid, or there is a feature that solves their problem.  That's great, and
the issue will not stick around and look like an open matter.  This is not the norm.  Even
so, these tell us things where we might have something more helpful in place for fielding
a particular case in the future.
>>>> In those cases, it is preferable to change the resolution.
>>>>> -----Original Message-----
>>>>> From: Andrea Pescetti []
>>>>> Sent: Sunday, March 20, 2016 14:09
>>>>> To:;
>>>>> 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.
>>>>> --------------------------------------------------------------------

I have been guilty of creating issues  for coding tasks because I like 
to see SVN commits that are tied to an issue.

Examples could be an update to the netbeans plugin or adding the 
bootstrap-connector to SVN, etc.

I think Resolved - Not an issue is most appropriate in these cases.

I never really asked if this is done by others.

Is this procedure used by others?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message