This question already has an answer here:

Take this recent (and highly irritating) bug for example. Our one and only Oded fixed it quickly but for the fix to actually have any effect, code must be "deployed" first, action that might take even days, especially now with SQL playing tricks on the team.

Until the fix is deployed, the bug still exists.

Two options:

  1. Mark since as far as the dev is concerned, it's fixed and it's just matter or time until all we enjoy it. That's by far the norm here in Meta.
  2. Bug exists so don't put any tag and wait until the fix is actually out there (maybe even wait for OP to confirm) before tagging as completed. Concern here is forgetting to tag leaving bug reports open even though they're actually fixed.

Personally I prefer #2 though it's really not that crucial. Can anyone see more aspects or reasoning in addition to what I brought here?

marked as duplicate by Martijn Pieters, animuson Nov 25 '13 at 21:14

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 3
    What is the problem with marking [meta-tag:status-completed] and putting the code revision? (As Oded did there) – Martin Smith Nov 25 '13 at 21:13
  • @MartinSmith it's confusing. User see status-completed and think "great, it's fixed!" just to find it's not only then bothering to read the dev answer and find out the rev still didn't update. – Shadow The Princess Wizard Nov 25 '13 at 21:17

Browse other questions tagged .