Document the release policy #749
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #749 +/- ##
==========================================
- Coverage 70.42% 70.39% -0.03%
==========================================
Files 96 96
Lines 16103 16103
Branches 2522 2522
==========================================
- Hits 11340 11336 -4
- Misses 4644 4648 +4
Partials 119 119 ☔ View full report in Codecov by Sentry. |
README.md
Outdated
|
|
||
| the template as fully as possible. Note that the `Bug report` template should | ||
| be used for all questions relating to a specific installation of BlueALSA, even | ||
| if you are not sure that it is a bug (the name of the template is set by |
There was a problem hiding this comment.
I don't think that it's set by GitHub... It's here: https://raw.githubusercontent.com/arkq/bluez-alsa/refs/heads/master/.github/ISSUE_TEMPLATE/1-bug-report.md and we can change it (and the name of the file itself). If you feel that Problem report is better wording (I'm not a native speaker, so for me bug/problem/issue is all the same more or less :D) you can update the template.
There was a problem hiding this comment.
I've had a look around some other projects and it seems that "Bug report" is very common, so perhaps that is best left as it is. I've removed the comment about github.
I'm thinking maybe the blank template should be removed, since so many issues are created with this when really the bug report template would have been more useful?
There was a problem hiding this comment.
I'm not sure whether the blank one can be removed. I don't think that it's configured anywhere...
There was a problem hiding this comment.
After some more thought, perhaps the blank template should remain, at least until there has been time to assess whether the new README text is helping. If it is ever decided to remove it, then I think there must be a way, because there are some other projects that have done so.
There was a problem hiding this comment.
Indeed it's possible to disable that blank template: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
borine
force-pushed
the
release-policy
branch
from
6fea150 to
cb9e9e5
Compare
Help users to understand how development is organized.