From 9e994cb11913a5ddd3a9bba3e54130f32fbd6008 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Fri, 15 Jun 2018 14:36:23 -0700 Subject: [PATCH] doc: wrap releases.md at 80 chars PR-URL: https://github.com/nodejs/node/pull/21361 Reviewed-By: Richard Lau Reviewed-By: Refael Ackermann Reviewed-By: Jon Moss Reviewed-By: Vse Mozhet Byt Reviewed-By: Luigi Pinca --- doc/releases.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/releases.md b/doc/releases.md index 902547ef994069..bbf70bbbfbee22 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -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 @@ -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