Re: FW: [EPICS Base R3.14.x 0000018]: gcc 2.95.x crashes on cac.cpp

[Andrew Johnson <anj@aps.anl.gov>]

Ralph Lange wrote:
>
> this is a good question - should bugs that turn up during development
> even be entered in the bug tracker?

I think so, but (if you know) the report should mention "Doesn't occur in
release R3.xx.yy".  I don't want bug reports to be spread out all over the
place because the system then gets too nebulous to be useful.  However
such bugs don't need the same visibility to non-developers as those that
appear in a release, so I'm happy that they be closed once the fix is in CVS.

> Looks a if this things needs a more precise concept ...

I changed the R3.14 Mantis News item to express when I think bugs should
be closed:

>> When to close a bug - 2002-11-05 09:17 - anj
>>
>> Resolved bugs in an official released version should only be closed
>> when they're fixed in a later official released version. This ensures
>> that known and fixed bugs are immediately visible to anyone who looks
>> on the View Bugs page. If a resolved bug has never appeared in an
>> official release it can be closed when resolved.
>>
>> The purpose here is to ensure that people reporting bugs in the latest
>> official release can see immediately if they have already been found
>> and fixed.

My philosophy is to try and make the website as useful as possible to
those people who are likely to actually use it.  I don't want to force
developers to jump through hoops unnecessarily (which putting CVS-only
bugs into a different project might do), but I also want to make it easy
for users to report problems and see what issues are already known about.
 The latest news item expresses how I think that can most easily be done.

- Andrew
--
"Life is what happens while you're busy making other plans." - John Lennon