1 Backport policy stable branches

Matthieu Gallien edited this page 2021-06-01 18:32:51 +02:00

Table of Contents

• Policy regarding the backports to stable branches
• Goals
• Some Guidelines

Policy regarding the backports to stable branches

Goals

• Does not include regressions (the goal is to never break a workflow that was working with the previous patch release) ;
• Provide fixes with stable branches (crash would be a good example, data loss if the fix is not invasive, ...) ;
• Should/Should not include string changes.

Some Guidelines

• If we are doing a X.Y.1 (usually one month after the X.Y.0 release) we may release quite some changes in particular we would try to fix most serious issues reported on X.Y.0 ;
• If we are doing a X.Y.2 (usually one month after the X.Y.1 release) we will backport trivial fixes even if the bug is not necessary critical but we are very confident that the fix will not introduce problems ;
• If we are doing a X.Y.3 (usually one month after the X.Y.2 release) we will only backport trivial fixes for serious bugs ;