Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed initial README #1

Closed
wants to merge 1 commit into from
Closed

Proposed initial README #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 14 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
# io.js Long-term Support Working Group

_See [issues](https://github.com/iojs/LTS/issues) for discussion on kicking off this working group._
## Goal

Define and execute a long-term support (LTS) plan for the io.js process.

1. Identify LTS branch points in the io.js repository and define lifecycle for each branch.
2. Clearly communicate the policy for each LTS branch, including how long it is expected to be supported and when it will be deprecated.
3. Monitor the io.js codebase for bug fixes and patches that should be backported to active LTS branches.
4. Set up a release process for each LTS branch, including a list of authorized releasers and a release methodology compatible with the methodology used for non-LTS io.js releases.
5. Monitor vendored dependencies, including libuv, V8 and OpenSSL for important updates that are compatible with the LTS release schedule.
6. Accept support responsibility for vendored dependencies that are no longer supported upstream.

## Working Group Members

_To be filled in_