During the development of the tool we occasionaly break things and then repair them, before the new release comes out. Currently, pull requests that fix these issues are labelled with the bug label. That leads to a number of fixed bugs showing up in the changelog, that weren't in the previous release. That makes the software look more buggy than it is and is also confusing to users. Therefore, it would be nice to come up with a better label for these issues and a better way to include them in the changelog. Does anyone have ideas on how to improve this?
Here are some ideas for labels:
bug_in_new_feature
development issue
followup
How do we present these in the changelog?
Let's discuss this at the next @ESMValGroup/technical-lead-development-team meeting.
During the development of the tool we occasionaly break things and then repair them, before the new release comes out. Currently, pull requests that fix these issues are labelled with the
buglabel. That leads to a number of fixed bugs showing up in the changelog, that weren't in the previous release. That makes the software look more buggy than it is and is also confusing to users. Therefore, it would be nice to come up with a better label for these issues and a better way to include them in the changelog. Does anyone have ideas on how to improve this?Here are some ideas for labels:
bug_in_new_featuredevelopment issuefollowupHow do we present these in the changelog?
Let's discuss this at the next @ESMValGroup/technical-lead-development-team meeting.