Relax restriction of one label per issue

[ghuntley]

Over at ReactiveUI we are not using the standard convention of:

- Bug
- Feature
- Improvement
- Performance

Instead, because the product targets so many platforms we use a convention of one label per platform:

- ReactiveUI Core
- ReactiveUI Events
- UWP
- Xamarin Android
- Xamarin Mac
- Xamarin iOS
- WPF
- WinForms
- Housekeeping

Currently GitReleaseManager has a restriction of one label per issue, in some cases a single GitHub issue will affect multiple platforms and thus would like to see that issue appearing multiple times in our release notes (i.e. once under Xamarin.Mac and once under Xamarin.iOS)

ITT we discuss design before sending in a PR.

[RichiCoder1]

Ditto. With Chocolatey GUI we categorize both by Type (Bug/Improvement/Feature), and Category (UI, Infrastructure, Chocolatey).

[RichiCoder1]

@ghuntley @gep13 I don't imagine this will be overly difficult to fix, so I'm thinking about doing a PR for this. Idea would be that there are these potential scenarios:

• Issue has no labels --> Exclude
• Issue has one label:
  • Label is excluded or doesn't match an included label or alias --> Exclude
  • Label is included --> Include and associate with label
• Issue has multiple labels:
  • No label matches an included label or alias --> Exclude
  • Only one label matches included label or alias --> Include and associate with label
  • Multiple labels match an included label or alias --> This is where it gets fuzzy. Should we include it based on the first matching label? Should we file it under every relevant label? Should we just excluded it? And if excluded, should it be silent or throw a warning or error?

[tbeu]

This current restriction is a real show-stopper. Unfortunately there is no other tool to automatically create release notes from a milestone.

[ghuntley]

#upforgrabs - watch dis video for more information