Documentation around highlighting PRs for release notes.

[jmchilton]

Introduces a new Github tag that lets contributors indicate they endorse including a PR in the user release notes and will do the work. This can be assigned by the PR author, reviewer, or any contributor willing to do the work to highlight the PR. The person assembling the user facing release notes will still have final say about what is included but this is a way of indicating to that person a strong preference for including a PR and willingness to help them do the work.

How to test the changes?

Does not apply.

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jdavcs]

If we formalize these, then, I think, we should also mention highlight/admin and highlight/dev in a similar manner. Both are intended as suggestions to include a PR in the full release notes (usually bullet point lists of significant admin- and dev-related updates).

Also, highlight/user will effectively replace the highlight/power-user label, right? (and that would be an improvement, I think)

[jdavcs]

I wonder, do we need to include this last sentence? I think it's clear that the final contents of the release notes is determined by the release team (the release manager, or a team, a committee, etc. - whatever it is), and not by the person who added the label. To me, the text seems to be a little too specific and prescriptive: we'd have to edit this page every time we change our approach. Same goes for the user label below.