Reicast-emulator: Re-organize the issue tracker

[skmp]

Follow up from #1381

We need to

• [ ] Go over tickets and roughly assign them to milestones (specific release, mid term, long term). This is more of a "guideline" right now, as we'll have to coordinate w/ developers to see if there are devs available
• [ ] Investigate how to best use github's project management tools. We have Issues, Labels, Projects, Milestones and Discussions. How do we want to use these tools?

[AbandonedCart]

The "catch-all" beta feedback issue is a train wreck.

[MrPsyMan]

I'm quite lost here @skmp

All in all, until the migration to cmake is finished and the split to libdc/frontend is done and both are thoroughly tested for regressions, additional planning is not viable.

[MrPsyMan]

@skmp we also overcomplicate things so far. There's no need for us to go through hell and back in order to do a submission (of code, issues, docs, etc.).

[AbandonedCart]

It seems like there needs to be some focus on organizing time, not just issues and documents. There shouldn't be a need to keep starting conversations over because of delays in response time. This is a combination of both organizing issues so the previous content is readily available and dedicating enough time to skim over it before attempting to resume discussion.

[luserx0]

46 Issue labels? Inhuman! (In-developer actually)
Our first priority and approach imho, should be stripping down the issue labels to the needed bare minimum and then filing in gaps.

My request is a WIP (Work In Progress) label to be added, as it helps me personally to see what I'm working on (yes, I'm forgetful).

[AbandonedCart]

A really bad trend is rather than adjusting / updating existing (fill in the blank), a new (fill in the blank) is added and then some of the previous content filters back into it.

The duplicate labels and all of the really unnecessary ones (ie. labels for game stuff that is now handled by gamesdb) have been removed. The rest will require actually reviewing relevance.

[luserx0]

@baka0815 @dmiller423 This seems rather stall, would you like to co-update the issue tracker and be done with it?