up vote 1 down vote favorite

I think the number one place where visitors to the MSE get peeved is with our usage of

They find something that doesn't work and then quite reasonably attach , but then we come in and say, "We prefer to only label those things as bugs which have been confirmed with WRI". Both sides of the coin are valid in my mind and I think we should stick with our community convention, but I wonder if it's worth creating or similar to handle cases where confirmation with WRI has not yet been obtained.

This may have been proposed before. I couldn't see it explicitly in the titles of any of the questions here. Worth bringing up again, at the minimum, though.

share
  • 12
    I think the standard so far has been "confirmed by the community", not "confirmed by WRI" and that makes more sense to me. If the issue is not really a bug, but a user misunderstanding, the experienced people here are quick in pointing it out. A support case number, or the support engineer's opinion, do not necessarily reflect the true status of a bug which is more in the domain of QA and R&D. – ilian Mar 11 at 17:22
  • 2
    As noted by @ilian, a suspected bug should not be tagged as such until "confirmed by the community". But, what constitutes confirmation? Do any guidelines exist? – bbgodfrey Mar 12 at 0:38
  • @bbgodfrey, Well, it seems to me that one guideline is that confirmed-by-WRI is sufficient :-) – m_goldberg Mar 12 at 20:10
  • Loose thoughts: I have mixed feelings about this. I was thinking about fixed-bug status/tag lately. There is also a combination of documentation+bugs. Or what about bugs in 3rd part packages? So there are clearly couple of types/states of bugs we are interested in. How to handle all of that in a consistent way, without using 2 tags per question, or without worrying about a flood of misplaced tags. There are voices saying this is not a place for a bug tracker which I think I agree with, otoh I would love to have one here :P – Kuba♦ Mar 14 at 21:34
up vote 3 down vote

I moved my old answer to a separate topic: Standard header for bugs-tagged posts V2

I don't think it will help with anything. What is the difference whether you tell OP to "not use bugs until it is confirmed" or "use suspected-bug until it is confirmed"?

And who will take care about cleaning up after this stage?

I think there should be only one tag: alternatively we can extend standard header

share

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .