Review and expand the stakeholders we communicate major changes to

@richard has created this checklist as part of the release process (which is awesome):

### notify stakeholders

* [ ] Email tor-qa mailing list: [tor-qa@lists.torproject.org](mailto:tor-qa@lists.torproject.org)
  * [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`
  * [ ] Call out any new functionality which needs testing
  * [ ] Link to any known issues
* [ ] Email Tails dev mailing list: [tails-dev@boum.org](mailto:tails-dev@boum.org)
  * [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`

And also:

### tor-announce mailing list

* [ ] Send an email to [tor-announce@lists.torproject.org](mailto:tor-announce@lists.torproject.org), using the same content as the blog post and subject "Tor Browser $version is released".

However it looks like we caught torbrowser-launcher unawares with the 12.0 release: https://github.com/micahflee/torbrowser-launcher/issues/659

We should take the opportunity to review how we notify external stakeholders during development, and expand this list to include Micah Lee & The Guardian Project at minimum (who don't necessarily have the time to read every tor-qa or tor-announce email).