From 2b9c4dc88ba19f937493d3f1b829b241268569ac Mon Sep 17 00:00:00 2001 From: Rod Vagg Date: Sun, 5 Apr 2015 22:42:07 +1000 Subject: [PATCH] initial readme --- README.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 143108c..828622b 100644 --- a/README.md +++ b/README.md @@ -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_