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

Jump to bottom

doc: update release management for 1.0 #714

Merged
merged 2 commits into from
Aug 21, 2023
Merged

doc: update release management for 1.0 #714

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
32e1240
update release management for 1.0
priteshbandi Jun 14, 2023
1686683
Update RELEASE_MANAGEMENT.md
priteshbandi Jun 14, 2023
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
6 changes: 2 additions & 4 deletions RELEASE_MANAGEMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The rest of the doc will cover the release process for the following kinds of re

### Major Releases

The Notation project is under active development to reach a stable target version of 1.0.0
The Notation project has reached a stable target version of 1.0.0 and all previous RC, BETA and ALPHA releases will no longer be supported.
priteshbandi marked this conversation as resolved.
Show resolved Hide resolved

### Minor Releases

Expand Down Expand Up @@ -53,9 +53,7 @@ The Notation project is under active development to reach a stable target versio

## Supported Releases

There aren't any stable releases of the Notation project currently. Once a stable version of Notation is released, that version will be supported as follow.

We expect to "support" n (current) and n-1 major.minor releases. "Support" means we expect users to be running that version in production. For example, when v1.3.0 comes out, v1.1.x will no longer be supported for patches and we encourage users to upgrade to a supported version as soon as possible. Support will be provided best effort by the maintainers via GitHub issues and pull requests.
We expect to "support" n (current) and n-1 major.minor releases. "Support" means we expect users to be running that version in production. For example, when v1.3.0 comes out, v1.1.x will no longer be supported for patches, and we encourage users to upgrade to a supported version as soon as possible. Support will be provided best effort by the maintainers via GitHub issues and pull requests.

We expect users to stay up-to-date with the versions of Notation they use in production, but understand that it may take time to upgrade. We expect users to be running approximately the latest patch release of a given minor release and encourage users to upgrade as soon as possible.

Expand Down