[Discuss] Bugtracker: avoiding duplicates

[Timothy Collett]

On Nov 2, 2006, at 4:37 AM, Tom wrote:
> I don't update the game code every day. Sometimes a bug is fixed,  
> but the fix isn't yet online.

Then perhaps you should wait to resolve/close a bug until it *is*  
online, so that people don't get confused.

If you set bugs you believe you've fixed to "feedback," it would also  
give people a chance to check whether it's actually fixed, and not  
have to open a new bug if it's not.  Then when it's been confirmed  
fixed on testing, you can set it Resolved, and when you upload it to  
stable, you can set it to Closed--that lets us know for certain what  
you know and what other people have verified about fixed bugs, rather  
than having to guess: "Is it really fixed?  Is it uploaded to stable  
yet?"

"Closed" bugs being still out there is definitely one of the #1  
confusing things to newbies about the bugtracker, and a system like  
this would, I believe, go a long way to alleviating that confusion.

Timothy Collett
Anaris Family

--

Military justice is to justice what military music is to music.
  -- Groucho Marx