Help SIG maintainers to keep track of spec changes

[svrnm]

With the spec having monthly releases the language SIGs need a way to (a) know about the changes and (b) have an approach to triage those changes when they happen to decide what requires an implementation right now and what not, e.g. because it's just a language fix in the spec or an experimental change that the SIG does not have bandwidth to tackle.

Before diving into a generalized solution, it would be great to know if and how SIGs are solving this problem today?

[mtwo]

Notes from maintainers meeting:

• @dyladan: it'd be nice to get this list as an issue / stream of issues into each SIG, instead of putting them in a place that most maintainers don't regularly read

[svrnm]

Just as a point of reference, there is a github action that is able to create issues through a workflow:

https://github.com/marketplace/actions/create-an-issue

It might not be necessary and using gh issue create directly in a workflow could do the trick as well, but it's a starting point.