Aleks, Am 10.01.19 um 15:30 schrieb Aleksandar Lazic: > In general I also see a huge benefit to add a issue tracker I also know > that's a > workflow change for the developers. > > As I also follow the discussion let suggest me the following. > > * add some templates for the different cases e. g.: ISSUE_TEMPLATE.md > https://blog.github.com/2016-02-17-issue-and-pull-request-templates/
Yes. We definitely need one template for "Bug" and another for "Wishlist". > * use some labels, as labels are very flexible and easy to use as selector. > for example: bug, 1.7, backport-1.7, 2.0-dev, fixed_in_1.9.1, ... I disagree here. We should not create too many labels, because one should not need to search for the proper labels. Also once an issue is marked closed it disappears from the view. Labels that make sense: - Affected version: affects/1.7, affects/1.8, ... - Type: Bug, Wishlist - Subsystem: dns, h2, ... - Resolution: fixed, invalid, cannot-reproduce, ... To track whether an issue is fixed in a specific branch Milestones + automated follow-up issues are superior. > * in the commit message(s) can the issue number be added to create a > corelation > to the issue with `#`. > https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests Yes, this should be done. Best regards Tim Düsterhus
