Chore: Create an issue template for new releases

[lalver1]

Closes #433

This PR creates an issue form template for new releases.

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.

[lalver1]

One small thing to note is that this template's checklist contains an item for the release candidate and another for the regular release. This may cause confusion about what to use in the title of the ticket (Make a Release: YYYY.0M.R or Make a Release: YYYY.0M.-rcR ), but it should be clear that the ticket should have the regular release version in the title, not the release candidate version.

We could add Release Type to the form (similar to benefits but with release-candidate and release instead of Regular and Hotfix) but it seems too much to have to create two separate issues, one for release candidates and one for releases.

[thekaveman]

...it should be clear that the ticket should have the regular release version in the title, not the release candidate version.

...it seems too much to have to create two separate issues, one for release candidates and one for releases.

Yeah we definitely don't want two separate issues! Since the checklist includes an item for making a release candidate, I think you're right and we're good with just the one template as-is.

[thekaveman]

@lalver1, can you see if it is possible to have a description / body in the issue that gets created?

E.g. it would be great if the text of the markdown field showed up in the issue, not just in the form for creating an issue from the template.

[lalver1]

That would be nice @thekaveman, I tried a few things on a test repo but unfortunately I couldn't get the text of the markdown field to show up in the issue; it looks like value is the only key you can set under attributes. So I also tried with the other types of form elements (textarea, checkboxes, etc.) but there wasn't anything I could use to get the behavior we want.

[angela-tran]

This looks great to me! It'll be so nice to use this rather than the copy-pasting we've been doing.