Hi Kou, Le 19/10/2022 à 06:29, Sutou Kouhei a écrit :
My proposal: We maintain the last major release: * We maintain 9.Y.Z when the latest major release is 9.0.0 * We may release 9.Y.Z when we find a problem such as a security vulnerability in 9.Y.Z * We drop support for 9.Y.Z when we release 10.0.0
That sounds ok to me, but is there a more precise criterion than "we find a problem"?
In the past, we have from time to time done maintenance releases based on annoying bugs/regressions. But not always.
I think that we can maintain multiple major releases with not high release cost by implementing the followings: * Green nightly CI * Nightly CI for all maintained branches (maint-X.Y.Z) * We need to reduce the time taken to CI * ...
I'm afraid "green nightly CI" is more of an ideal than a reality given the breadth and complexity of our fleet of CI jobs. We still seem to have stability problems in some areas (perhaps Acero?) but there are also regularly regressions due to changes in third-party packages.
Regards Antoine.
