[ Documentation] Create a Pinned Locked Issue For People to Follow Updates

[yordis]

Hey there,

I am really interested in following what is happening with this feature, currently, I subscribe to absolutely everything that is going on but I can't keep up with it anymore.

I would like the committee to create a locked issue solely for the committee to give updates to the general public, potentially pinning the issue for discoverability and people that are interested in following the progression like me.

🙏🏻

[voronoipotato]

Isn't that what the history.md is for? I know things have been moving a bit fast to document, but mostly it's just been talking afaict.

[yordis]

@voronoipotato totally would make sense from your perspective, but I cant figure out how to subscribe to a file change type of situation.

I would subscribe to all PRs but honestly, sometimes they suffer from the same issues that are happening, so I personally would appreciate if TC39 would take ownership of creating a ticket just for that 🙏🏻

[js-choi]

We could use GitHub Releases to mark “significant” changes to the explainer or spec. I’m not sure what would count as “significant” changes, though. Things might include:

• Switching from ^ to another token for the topic reference (see Bikeshedding the Hack topic token #91).
• Adding new sections, such as FAQ sections, to the explainer.
• Changes in the proposal’s Stage.
• Corrections to spec bugs?
• Other ideas?

CC: @tabatkins, for later.

[tabatkins]

I like a pinned locked issue to track major progress. I use that to notify about major/breaking changes for another project of mine; it seems to be useful. Let's go with that.

[js-choi]

Something like speced/bikeshed#321, right?

[tabatkins]

yup

[js-choi]

Fixed by #232.

[yordis]

Thank you so much you'all