[2021-02-04] Write a list of topics to cover in GraphQL spec release marketing

[benjie]

Lee: why are we doing this? Reference implementations and community implementations tend to track the draft, so the "cut" spec is mostly an artifact. What's the value beyond the legal process? Having a moment in time to look at the work that went into it and reflect on it - "let's look back at all the work that's gone into GraphQL in the last 18 months." It's to let the people who've been doing the work talk about what doing the work was like, what it enables, why. What's it like when you find an ambiguity and want to write a spec change to solve it?
Lee: What we can do is create a schedule that draws attention to these blog posts
Lee: We are just going to collect the ones that we’ve written and a stories that we want to tell and aggregate them
ACTION - Lee and Brian: write a list of the things you definitely want covered

See also #637

• assignee(s): @leebyron and @brianwarner
• source: https://github.com/graphql/graphql-wg/blob/main/notes/2021-02-04.md#promoting-and-documenting-spec-release-5m-brian

---

Note: Action Item issues are reviewed and closed during Working Group
meetings.

[benjie]

Related: Write Changelog for next spec release.

[benjie]

Ready for review due to graphql/graphql-spec#871