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

Update governance #102

Merged
merged 1 commit into from
Jul 13, 2023
Merged

Update governance #102

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
5 changes: 2 additions & 3 deletions _pages/governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ The main branch is where all accepted changes are first committed. The CI loop i

### Release branches

A release branch is created from the main branch at the time of feature freeze for the release.
A release branch is created from the main branch on the release, for maintenance.

### Release Tags

Expand Down Expand Up @@ -183,8 +183,7 @@ Specifically out of scope would be the APIs internal to the Linux kernel. The Li

#### Adding New APIs

A new API shall not break the existing one. In such case the deprecating
APIs process described below shall be applied.
An update of the API shall not break the existing one. When possible a new API should be created instead of updating the existing one, else the deprecating APIs process described below shall be applied.

#### Deprecating Existing APIs

Expand Down