Keep the release process example aligned with the current Ubuntu LTS used by the project containers.
Assisted-by: GPT-5.6-Luna, OpenCode Signed-off-by: Ales Musil <[email protected]> --- Documentation/internals/release-process.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/internals/release-process.rst b/Documentation/internals/release-process.rst index 03bbb4163..f5a3ec1fa 100644 --- a/Documentation/internals/release-process.rst +++ b/Documentation/internals/release-process.rst @@ -66,8 +66,8 @@ Scheduling`_ for the timing of each stage: and risk and discussed on ovs-dev before creating the branch. In order to keep the CI stable on the new release branch, the Ubuntu - container should be pinned to the current LTS version in the Dockerfile - e.g. registry.hub.docker.com/library/ubuntu:22.04. + container should be pinned to the LTS version used by the project's + container Dockerfile, e.g. registry.hub.docker.com/library/ubuntu:24.04. 3. When committers come to rough consensus that the release is ready, they release the .0 release on its branch, e.g. 25.09.0 for branch-25.09. To -- 2.55.0 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
