daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: update announce documentation for releases 

This updates the announce section to match the current
process of announcing releases on Node.js. This also
mentions the latest Bluesky automation.

PR-URL: https://github.com/nodejs/node/pull/56200
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Ruy Adorno <ruy@vlt.sh>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
pull/56329/head
Rafael Gonzaga 2024-12-11 16:08:22 -03:00 committed by Ruy Adorno
parent 44c4e57e32
commit 7a94100a3e
No known key found for this signature in database
GPG Key ID: 97B01419BD92F80A
1 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/contributing/releases.md
View File

@ -1090,20 +1090,18 @@ This script will use the promoted builds and changelog to generate the post. Run
### 19. Announce
The nodejs.org website will automatically rebuild and include the new version.
To announce the build on Twitter through the official @nodejs account, email
<pr@nodejs.org> with a message such as:
To announce the build on social media, please ping the @nodejs-social-team
on offical slack channel.
Node.js is also available on Bluesky and a release announcement can be
reposted using [nodejs/bluesky](https://github.com/nodejs/bluesky) repository.
The post content can be as simple as:
> v5.8.0 of @nodejs is out: <https://nodejs.org/en/blog/release/v5.8.0/>
> …
> something here about notable changes
To ensure communication goes out with the timing of the blog post, please allow
24 hour prior notice. If known, please include the date and time the release
will be shared with the community in the email to coordinate these
announcements.
Ping the IRC ops and the other [Partner Communities][] liaisons.
<details>
<summary>Security release</summary>
@ -1437,7 +1435,6 @@ Typical resolution: sign the release again.
[Build issue tracker]: https://github.com/nodejs/build/issues/new
[CI lockdown procedure]: https://github.com/nodejs/build/blob/HEAD/doc/jenkins-guide.md#restricting-access-for-security-releases
[Node.js Snap management repository]: https://github.com/nodejs/snap
[Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md
[Snap]: https://snapcraft.io/node
[`create-release-proposal`]: https://github.com/nodejs/node/actions/workflows/create-release-proposal.yml
[build-infra team]: https://github.com/orgs/nodejs/teams/build-infra