Hi all,

A recent thread [1] had several topics of discussion come up about proposed changes to OVN release management. This thread is specifically to discuss the support lifetime of OVN releases.

Current documentation discusses two ideas with regards to version support lifetime * LTS releases receive two years of bugfixes, and an additional year of critical/security fixes. * When an issue is fixed in OVN, we fix it in main first, then backport all the way to the most recent LTS.

In this thread, I propose the following revisions should be made to the OVN documentation:

* "Supported" versions refers to versions for which we are providing minor releases [2] . "Unsupported" versions are versions for which we are no longer providing regular minor releases. An unsupported version may still receive changes to its development branch, but there will be no further releases made on that branch.

* Standard support (non-LTS) versions will be supported for one year from the time of its initial release.

* Instead of backporting fixes to the most recent LTS, we will backport fixes to the previous 4 branches. This means that we will be providing fixes to branches of unsupported versions.

* Critical/security fixes should be backported to all branches between the current main branch and the branch corresponding to the LTS version that is currently receiving critical/security fixes. This means that we will be porting the fix to unsupported versions. The fix will be present in those branches, but we will not create releases for those unsupported versions.

Please let me know if you have questions or objections to these policy changes.

Thanks,
Mark Michelson

[1] https://mail.openvswitch.org/pipermail/ovs-dev/2023-April/403736.html (best of luck) [2] I am starting a separate thread on this list where we will discuss the current policy regarding minor releases.

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to