This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
meta: add release working group #167
Closed
Closed
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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) | ||
|
@@ -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 | ||
the release and support process for all releases | ||
|
||
Responsibilities include: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove one of the "Responsibilities include:" :-D There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. HA! Sigh There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: For clarity, it might be good to use |
||
these branches. | ||
* Define the policy for what gets backported to release streams. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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: