Skip to content

Note when to backport changes #1169

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

Merged
hugovk merged 6 commits into from
Oct 6, 2023
Merged

Note when to backport changes #1169

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
35e855b
docs(#1168): add directive on backporting
JacobCoffee Sep 28, 2023
9e91c45
fix(docs): apply suggestions
JacobCoffee Sep 28, 2023
05cfc3f
Update developer-workflow/development-cycle.rst
JacobCoffee Sep 29, 2023
5bd59e2
Update developer-workflow/development-cycle.rst
JacobCoffee Oct 5, 2023
7b9bff6
Update developer-workflow/development-cycle.rst
JacobCoffee Oct 5, 2023
4b7de3a
Update developer-workflow/development-cycle.rst
JacobCoffee Oct 5, 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
Prev Previous commit
Update developer-workflow/development-cycle.rst 
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
  • Loading branch information
@JacobCoffee @hugovk
JacobCoffee and hugovk authored Oct 5, 2023
commit 4b7de3a94394acac68c736ed043425c122e67dad
2 changes: 1 addition & 1 deletion developer-workflow/development-cycle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ releases; the terms are used interchangeably. These releases have a

The only changes allowed to occur in a maintenance branch without debate are
bug fixes, test improvements, and edits to the documentation.
Also, a general rule for maintenance branches is that compatibility
Also, a general rule for maintenance branches is that compatibility
must not be broken at any point between sibling micro releases (3.5.1, 3.5.2,
etc.). For both rules, only rare exceptions are accepted and **must** be
discussed first.
Expand Down