meta,doc: ping community about new release#24064
meta,doc: ping community about new release#24064refack wants to merge 1 commit intonodejs:masterfrom
Conversation
refack
added
the
meta
| will be shared with the community in the email to coordinate these | ||
| announcements. | ||
|
|
||
| Ping the IRC ops and the other [Partner Communities] liaisons. |
There was a problem hiding this comment.
Are there any handles? Also, not sure which IRC channel this would be..#node-build?
There was a problem hiding this comment.
Probably #node-dev, as for handles, if they are not online they won't see the notification, so I'd say mention those who are online, e.g.:
There was a problem hiding this comment.
Even just a message in #node-build and/or #node-dev would be immensely helpful.
There was a problem hiding this comment.
| Ping the IRC ops and the other [Partner Communities] liaisons. | |
| Mention the new release in [freenode#node-build], this should sync with our other [Partner Communities] and inform our liaisons. | |
| [freenode#node-build]: https://www.irccloud.com/irc/freenode/channel/node-build |
There was a problem hiding this comment.
This seems like something we should automate rather than do manually
There was a problem hiding this comment.
Like 90% of the things in this guide that are still manual 😅
|
I am not in Node Slackers. How do I know who their liaisons are / how to contact them? |
|
@targos it me, if you ping in irc that’s more than sufficient :-) |
I linked to https://github.com/nodejs/community-committee/blob/master/PARTNER_COMMUNITIES.md which ref @ljharb as the liaison. |
Sorry, nodejs/community-committee#410 needs to land first. |
refack
added
the
author ready
|
Landed in 17e4213 |
PR-URL: nodejs#24064 Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
|
I feel like we need a moratorium on adding additional steps to the release procedure, it's getting out of hand. Add on the extra items for security releases and it's a massive burden. A focus on tooling to improve things might be good. |
PR-URL: #24064 Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
PR-URL: #24064 Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
PR-URL: #24064 Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
PR-URL: #24064 Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
9 participants
Ping the IRC ops and the other [Partner Communities] liaisons.Refs: http://logs.libuv.org/node-build/2018-11-03#16:44:59.388
/CC @nodejs/releasers @ljharb @dshaw
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes