[Ohrrpgce] Bugtracker release tags

[Ralph Versteegen]

The categorisation of bugs in our bug trackers by release has always
bothered me because it wasn't clear what the release actually meant
(present in? introduced in? fixed in? vague guess?) or whether it was set
correctly, especially the 'nightly' tag.

So I propose a simple rule on github:
-Add a single release tag, which is the earliest release (or 'nightly') in
which the bug is known (or purported) to be present in. Use the 'ancient'
tag instead if the bug has clearly been around a long time. Don't tag if
unknown.
-If the bug is known to have been introduced in the tagged
release/nightlies, then add the "Is new in ..." tag.
-When we do a stable release, all bugs tagged 'nightly' which are still
open should be re-tagged with the new release. Any closed bugs tagged
'nightly'... I guess we just keep them as they are.

Tags for operating systems were also a big mess previously. OS tags should
only be used if actually relevant.

I've checked that the issues currently on github comply with this (most
aren't tagged by release). When bugzilla and sourceforge bugs finally get
imported (I want to try again soon), I'll try to homogenise tags/categories
across the different trackers, and will replace "nightly" on open bugs with
something else. So just beware that old bugs might be inconsistent. I think
I'll just remove the OS tags completely (and put that in the description
instead).

We can also create a milestone per release and add fixed bugs to the
milestone in which they were fixed. (Open bugs added to milestones are a
todo list)

I'm also going to follow the same scheme with the bughunters league table,
but moving forward I want to get into the habit of filing bugs of GH
instead putting them in that table. Unless I fix them immediately or
they're trivial (glitches), I guess.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.motherhamster.org/pipermail/ohrrpgce-motherhamster.org/attachments/20200127/51d41d5c/attachment.html>