When should bug tracker issues be tagged with a version?
Posted: 01 Aug 2017, 21:56
So now that I have bug tracker access (thanks lgromanowski!) I thought I might try to triage a couple of issues. Some of them were things marking things as "confirmed" when someone has confirmed that the issue was.
However, I'm really confused as to when things should be tagged with a certain version. There were several issues that were marked as "Confirmed", but had no issue. I thought that tagging them as OpenMW 0.43 would be a good thing, since then they get visibility on the roadmap page. However, several of these version tags were then removed.
Apparently, there is some unwritten rule I'm not aware of for when issues should be tagged with a version. When does this happen? When it's confirmed? When it's assigned? When it's resolved? Something else?
However, I'm really confused as to when things should be tagged with a certain version. There were several issues that were marked as "Confirmed", but had no issue. I thought that tagging them as OpenMW 0.43 would be a good thing, since then they get visibility on the roadmap page. However, several of these version tags were then removed.
Apparently, there is some unwritten rule I'm not aware of for when issues should be tagged with a version. When does this happen? When it's confirmed? When it's assigned? When it's resolved? Something else?