Closed
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
Description
I'm attempting to start discussion about how an LTS for io.js would work: who would run it and what it might look like. We need to form a working group of appropriately skilled people with time to maintain this thing and they will be the ultimate arbiters of how this is run but community input is important at this early stage.
To discuss, head over to:
- Proposed initial README (just some goals)
- Working group membership (my initial proposed list)
- TLS branch selection & lifecycle
- Release mechanics
- Adding special features to LTS branches
Please be aware that many people involved in this are time-poor, so please think carefully before commenting, if you don't have anything constructive to add then maybe hold back, and that includes +1's.
Metadata
Metadata
Assignees
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
Activity
[-]LTS WG Kickoff[/-][+]LTS Working Group Kickoff[/+]Fishrock123 commentedon May 14, 2015
I wouldn't mind joining this short term, as I'm probably going to be doing some of the dirty work. (see: #1560)
aredridel commentedon May 15, 2015
How does this overlap with the ideas in https://github.com/jasnell/dev-policy#long-term-support-working-group-roadmap ?
totherik commentedon May 15, 2015
Also nodejs/dev-policy#67 ?
Fishrock123 commentedon Jun 28, 2015
Deferring to https://github.com/nodejs/LTS