+1 to move the table to the web site. I'm also thinking the download page is a good place to put the table if we don't want to start a new page.
On Sat, 9 Nov 2024 at 07:36, Ethan Rose <er...@apache.org> wrote: > +1 for moving supported version list to the website and out of the release > artifact. As Attila said, this is a living document so it does not really > fit into immutable releases. We can find a place for it in the old and new > website, but my first guess would be to put it on the downloads page which > already has a table of releases and their links. > > Ethan > > On Fri, Nov 8, 2024 at 2:36 PM Attila Doroszlai <adorosz...@apache.org> > wrote: > > > > I'm ok with either having this in the SECURITY.md file or tracking this > > in > > > the Ozone website. (We can even do both) > > > > - The list of releases supported is going to change in time, but > > release artifacts are immutable. How do we invalidate the list > > included in an old release? > > - Multiple release lines may be supported at the same time, and > > releases may be interleaved (1.4.1, 2.0.0, 1.4.2, etc.). It's not > > clear which list invalidates which other lists. > > > > I think we should simply move it to the website, where we can have a > > single list, and change it with or without making a new release. > > > > -Attila > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > > For additional commands, e-mail: dev-h...@ozone.apache.org > > > > >
