From 4118574487f3c5e340d4790bc505d7480e528749 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 22 Jan 2019 11:09:15 -0500 Subject: [PATCH 1/2] doc: update to reflect N-API Update to indicate that changes for N-API will be allowed in Maintenance when necessary. --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2c824ed..5f81562 100644 --- a/README.md +++ b/README.md @@ -112,12 +112,19 @@ weeks before being backported. It is possible for a commit to land earlier at the discretion of the Release working group and the maintainers of the LTS branches. Once a release moves into Maintenance mode, only ***critical*** bugs, -***critical*** security fixes, and documentation updates will be permitted. +***critical*** security fixes, documentation updates, and updates to ensure +consistency and usability of the N-API across LTS releases will be permitted. +Unless a change is ***urgent*** it will be planned into a release once per +quarter. Such releases will only be made when necessary. Note that while it is possible that critical security and bug fixes may lead to *semver-major* changes landing within an LTS stream, such situations will be rare and will land as *semver-minor* bumps in the LTS covered version. +Upates to ensure consistency and usability of the N-API across LTS releases +are allowed as it is important to ensure that N-API native modules can be used +across LTS versions in order to support adoption. + All LTS releases will be assigned a codename. A list of expected upcoming codenames is available in [CODENAMES.md](./CODENAMES.md). From 8a4677b7728446c266d9d651a57f8c94c053418f Mon Sep 17 00:00:00 2001 From: Vse Mozhet Byt Date: Wed, 23 Jan 2019 10:43:38 -0500 Subject: [PATCH 2/2] squash: accept suggestion Co-Authored-By: mhdawson --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5f81562..720853f 100644 --- a/README.md +++ b/README.md @@ -121,7 +121,7 @@ Note that while it is possible that critical security and bug fixes may lead to *semver-major* changes landing within an LTS stream, such situations will be rare and will land as *semver-minor* bumps in the LTS covered version. -Upates to ensure consistency and usability of the N-API across LTS releases +Updates to ensure consistency and usability of the N-API across LTS releases are allowed as it is important to ensure that N-API native modules can be used across LTS versions in order to support adoption.