Skip to content

Commit

Permalink
doc: wrap releases.md at 80 chars
Browse files Browse the repository at this point in the history
PR-URL: #21361
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
  • Loading branch information
Trott authored and targos committed Jun 16, 2018
1 parent 529d24e commit 9e994cb
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions doc/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,8 +88,8 @@ least one business day in advance of the expected release. Coordinating with
Build is essential to make sure that the CI works, release files are published,
and the release blog post is available on the project website.

Build can be contacted best by opening up an issue on the [Build issue tracker][],
and by posting in `#node-build` on [webchat.freenode.net][].
Build can be contacted best by opening up an issue on the [Build issue
tracker][], and by posting in `#node-build` on [webchat.freenode.net][].

When preparing a security release, contact Build at least two weekdays in
advance of the expected release. To ensure that the security patch(es) can be
Expand Down Expand Up @@ -524,7 +524,8 @@ To announce the build on Twitter through the official @nodejs account, email

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.
will be shared with the community in the email to coordinate these
announcements.

### 16. Cleanup

Expand Down

0 comments on commit 9e994cb

Please sign in to comment.