Commit 9e994cb
doc: wrap releases.md at 80 chars
PR-URL: #21361
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 529d24e commit 9e994cb
1 file changed
Lines changed: 4 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -88,8 +88,8 @@ least one business day in advance of the expected release. Coordinating with | |||
| 88 | 88 | Build is essential to make sure that the CI works, release files are published, | |
| 89 | 89 | and the release blog post is available on the project website. | |
| 90 | 90 | ||
| 91 | - Build can be contacted best by opening up an issue on the [Build issue tracker][], | ||
| 92 | - and by posting in `#node-build` on [webchat.freenode.net][]. | ||
| 91 | + Build can be contacted best by opening up an issue on the [Build issue | ||
| 92 | + tracker][], and by posting in `#node-build` on [webchat.freenode.net][]. | ||
| 93 | 93 | ||
| 94 | 94 | When preparing a security release, contact Build at least two weekdays in | |
| 95 | 95 | advance of the expected release. To ensure that the security patch(es) can be | |
@@ -524,7 +524,8 @@ To announce the build on Twitter through the official @nodejs account, email | |||
| 524 | 524 | ||
| 525 | 525 | To ensure communication goes out with the timing of the blog post, please allow | |
| 526 | 526 | 24 hour prior notice. If known, please include the date and time the release | |
| 527 | - will be shared with the community in the email to coordinate these announcements. | ||
| 527 | + will be shared with the community in the email to coordinate these | ||
| 528 | + announcements. | ||
| 528 | 529 | ||
| 529 | 530 | ### 16. Cleanup | |
| 530 | 531 | ||
0 commit comments