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

docs: document the policy for backporting documentation changes #16137

Merged
merged 1 commit into from
May 28, 2021
Merged

docs: document the policy for backporting documentation changes #16137

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions Documentation/contributing/release/backports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,17 @@ the release of version ``v1.3.0``:
- Major bugfixes relevant to the correct operation of Cilium
- Debug tool improvements

Backport Criteria for documentation changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Changes to Cilium's documentation should generally be subject to backports for
all supported branches to which they apply (all supported branches containing
the parent features to which the modified sections relate).

The motivation is that users can then simply look at the branch of the
documentation related to the version they are deploying, and find the latest
correct instructions for their version.

Proposing PRs for backporting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down