Bug #51224
Updated by Loïc Dachary almost 3 years ago
ceph-backports.sh so must refuse to create a backport for octopus if the matching backport for pacific is not merged yet (with a --force option because there presumably are exceptions). It is always better to stage, test, merge and release a backport in release N before doing the same for release N-1. However, people and processes in place for each stage are different. Someone willing to help with the backports by reading "the backport submission documentation":https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst may not fully understand the need for this ordering. If such a person tries to stage a backport for N-1 and is shown the message: "this was not merged in N, please work on that before (or use --force if you know what you're doing)", they will hopefully redirect their efforts to stage a backport for N, therefore helping with the ordering of backports.