On 5/25/23 20:22, Mark Michelson wrote: > The OVN team has had no concrete policy regarding when releases are > made for a given version. In the past, new releases have been made only > when something critical has been found, meaning that most bug fixes > applied to a given OVN version never end up in a release. > > This change proposes a monthly release per supported OVN version. > > Signed-off-by: Mark Michelson <mmich...@redhat.com> > --- > Documentation/internals/release-process.rst | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/internals/release-process.rst > b/Documentation/internals/release-process.rst > index 1f4b90143..0287795dc 100644 > --- a/Documentation/internals/release-process.rst > +++ b/Documentation/internals/release-process.rst > @@ -152,6 +152,12 @@ approximate: > | T + 6 | Sep 1, Mar 1, ... | Release version x.y.0 > | > > +---------------+---------------------+--------------------------------------+ > > +After the .0 release is created for a given OVN version, that version will > have > +releases made every month until its support lifetime has concluded. If for > some > +reason, no changes occur to a supported OVN version during a month, then no > +release will be made that month. Therefore, there is no guarantee about the > +exact number of releases to be expected for any given OVN version. > + > Release Calendar > ---------------- >
It makes sense but (I think I may have mentioned this during an upstream meeting) can we automate the process? It's going to be 2 patches per release, 2 standard term releases + 2 LTS releases, release every month => 96 patches to ack throughout the year (unless my reasoning is wrong). Regards, Dumitru _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
