Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

meta: add release working group #167

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions WORKING_GROUPS.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ Top Level Working Group](https://github.com/nodejs/TSC/blob/master/WORKING_GROUP
* [Benchmarking](#benchmarking)
* [Post-mortem](#post-mortem)
* [Intl](#intl)
* [Release](#release)


### [Website](https://github.com/nodejs/nodejs.org)
Expand Down Expand Up @@ -248,3 +249,18 @@ Responsibilities include:
to be generated when needed.
* Defining and adding common structures to the dumps generated
in order to support tools that want to introspect those dumps.

### [Release](https://github.com/nodejs/release)

The purpose of the release Working Group is to manage/execute
Copy link
Member

@Trott Trott Aug 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the passive voice here. Also, release Working Group -> Release Working Group. Also, release...process for all releases is a head-scratcher. And this sentence needs a period at the end.

Here's what I'd do:

The Release Working Group manages the release process for Node.js. Responsibilities include:

the release and support process for all releases

Responsibilities include:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove one of the "Responsibilities include:" :-D

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HA! Sigh

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit messages is 💯 on this one.

* Define the release process.
* Define the content of releases.
* Generate and create releases.
* Test Releases.
* Manage the LTS and Current branches including backporting changes to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: For clarity, it might be good to use Long-Term Support rather than LTS here.

these branches.
* Define the policy for what gets backported to release streams.