> 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

Reply via email to