Ideas for more "topic" labels #4129
Replies: 6 comments 7 replies
-
|
I do like |
Beta Was this translation helpful? Give feedback.
-
|
Just updated #3920 with your first two labels and two additional ones we agreed on! |
Beta Was this translation helpful? Give feedback.
-
|
There should be some kind of art label for all the art related issues and stuff (such as topic: art). It'd allow any contributors that either have skills in or specialise in art to more easily find them and fix them. |
Beta Was this translation helpful? Give feedback.
-
|
We're currently discussing which |
Beta Was this translation helpful? Give feedback.
-
|
I just got another idea - a label for bugs reproducible on the latest version. I originally thought a label for each version but this works better. It'd be much easier to track which bugs still need to be solved and which ones don't / need reproducing and I/others wouldn't have to go "can this be reproduced on x.x.x?" |
Beta Was this translation helpful? Give feedback.
-
|
... So |
Beta Was this translation helpful? Give feedback.
-
|
Well, for example, this issue #2676 was classified as bug reproduced even though it was on an old version. If there was an additional label to note that it's been reproduced on the latest version (and said label gets automatically removed with a new release) then this issue would of gotten tested every version to get the label back, and if it couldn't then it would have been close awhile ago. Like, every time a new version is put up, all the bugs with the 'reproducible on the latest version' label would have it automatically removed, then that'd be a hint for people to test reproducing the bug on the latest version to get the label back, and if it can't, then it's likely been fixed with some changes and no one noticed. But then again, the example I used did get tested on a new version and wasn't reproducible, it just didn't get the label for it/ further investigation leading to it being closed, so this label's only use is a failsafe/backup if a moderation team doesn't exist or doesn't interact with an issue at all? It's doesn't have that much use now that I'm thinking about it, but maybe someone else thinks otherwise? |
Beta Was this translation helpful? Give feedback.
-
|
Hundrec's response:
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, if the bug CAN'T be reproduced on the latest version, then it should probably be closed as resolved. |
Beta Was this translation helpful? Give feedback.
-
|
Develop build label (for issues that only happen on or are related to the develop build). For example: |
Beta Was this translation helpful? Give feedback.
-
|
Personally I think this is redundant since the issue template already has an option indicating that you’re compiling from source. |
Beta Was this translation helpful? Give feedback.
-
|
This would be redundant since if a bug only occurs in the |
Beta Was this translation helpful? Give feedback.
-
|
Pending internal PR |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
"Topic" labels are a great way for making the issues and pull requests more distinct. However, it has bothered me a bit that some don't have them because there doesn't exist an appropriate "topic" label . So here are some of my ideas for additional "topic" labels:
topic: save datatopic: stage editortopic: chart editorlabel but for the Stage Editor.i am biased for this onetopic: gameplaytopic: menustopic: cutscenestopic: generaltopic: miscellaneousObviously all of these are just my ideas and are negotiable. Any criticism towards these is fully acceptable and encouraged! Thank you for reading!
Beta Was this translation helpful? Give feedback.
All reactions