If I have 100 bugs and Ill set 50 of them to have a tag lets say "3.3" it mean all there bugs must be fixed for that release. I cant let the same tag in issues when the same branch is in release. To me doesn't make sense. When I set out a release, that correspondent tag have no sense to be in code any more. All bugs not fixed will gain the next tag - eg.: "3.4". While in release mode when people will find bugs they have be in a "know issues" list until next release where they will be or not fixed. In my point of view there is not such "we aim". Instead I have "that's is the current deadline to fix them," if the deadline is to optimistic means someone did something wrong with the schedule. It doesn't matter is the project is open source or not. I simple say: we didn't fix all bugs for this release but "we aim" to the next release.
TDLR: Release tag cant exist in opened issues.
- It can be like "3.3 -> 3.4" (the means : we cant fix it in 3.3 we aim to be fixed in 3.4" but it will be a temporary tag until all issue will be update with the next tag.
Now, lets talk abut my current issues: I use Linux but not Mint: Debian 10 instead.
The two godot version in your link do not have any of the two issue from me posted in github - However, I use mono version.
The you want me to test the beta version and the RC. Usually I do it - not so often because I try to be focused in other activity like: making my game ;), art (oil painting), nature (environmental scientist), people (counsellor) to mention some..
(typical infj I can say :))
