| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -272,10 +272,12 @@ Create a new blog post by running the [nodejs.org release-post.js script](https: | |||
| 272 | 272 | ||
| 273 | 273 | ### 15. Announce | |
| 274 | 274 | ||
| 275 | - The nodejs.org website will automatically rebuild and include the new version. You simply need to announce the build, preferably via Twitter with a message such as: | ||
| 275 | + 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](pr@nodejs.org) with a message such as: | ||
| 276 | 276 | ||
| 277 | 277 | > v5.8.0 of @nodejs is out: https://nodejs.org/en/blog/release/v5.8.0/ … something here about notable changes | |
| 278 | 278 | ||
| 279 | + 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. | ||
| 280 | + | ||
| 279 | 281 | ### 16. Cleanup | |
| 280 | 282 | ||
| 281 | 283 | Close your release proposal PR and remove the proposal branch. | |
| Back | FazBrowse Home | New Git URL |
0 commit comments