Re: [VOTE] Apache Ozone 1.4.1 RC2

> > Does anyone know what this "white_check_mark" means? My understanding is that the "white_check_mark" denotes that the particular release is currently supported and the user can expect minor releases with security fixes. This means if there are any security issues identified in the supported re

Re: [VOTE] Apache Ozone 1.4.1 RC2

Does anyone know what this "white_check_mark" means? Do we really need this "Version, Supported" table in this SECURITY.md file, can we remove it? On Thu, 7 Nov 2024 at 00:55, Ethan Rose wrote: > Yes we should add a step in the guide to update the security file with the > current release when a

Re: [VOTE] Apache Ozone 1.4.1 RC2

Hi Ethan Rose Thanks for the update. I'm wondering if our current Ozone-1.4-RC2 vote should continue? Or if I need to update “SECURITY.md”, release Ozone-1.4-RC3 and vote again? Xi Chen On 2024/11/06 16:54:17 Ethan Rose wrote: > Yes we should add a step in the guide to update the security file

Re: [VOTE] Apache Ozone 1.4.1 RC2

Yes we should add a step in the guide to update the security file with the current release when a new one goes out. Thanks Nanda for catching this. I had been tracking updates required to the guide as part of this release process locally but hadn't shared anything yet. I just filed HDDS-11654

Re: [VOTE] Apache Ozone 1.4.1 RC2

Hi Nanda Thanks for your check and suggestions Q: The code name for the release is still set to "Hot Springs" which is of 1.4.0, should we use a new name for 1.4.1? A: Currently, Ozone only changes the national park tag when it releases the master branch, The minor branch release maintains the