On 29/08/2025 12:27, Ilya Maximets wrote: > On 8/29/25 1:13 PM, Kevin Traynor wrote: >> On 29/08/2025 11:42, Ilya Maximets wrote: >>> This will be the final release of OVS 3.2 as it reached its end of support >>> with release of OVS 3.6. >>> >> >> Maybe we should put above in the v3.2.6 NEWS as below kind of suggests >> there will be another 3.2 release? > > We're normally adding such a patch to EoL branches, so if someone is using the > branch downstream with their own custom backports, they will have a version > difference with the actual upstream release. It's not necessary, but it's > nice > to have it, I think. It's the same as with non-EoL releases, if someone is > using > the branch directly (maybe with custom patches), they have a +1 version. > > Does that make sense? >
ok, sure, if there may be some benefit then let's keep it. Thanks. >> >>> --- a/NEWS >>> +++ b/NEWS >>> @@ -1,3 +1,6 @@ >>> +v3.2.7 - xx xxx xxxx >>> +-------------------- >> >> I think we may have discussed before but I don't remember the details. >> It's not a blocking issue, so either way: >> >> Acked-by: Kevin Traynor <[email protected]> >> >>> Ilya Maximets (2): >>> Set release date for 3.2.6. >>> Prepare for 3.2.7. >>> >>> NEWS | 6 +++++- >>> configure.ac | 2 +- >>> debian/changelog | 8 +++++++- >>> 3 files changed, 13 insertions(+), 3 deletions(-) >>> >> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
