Hi Ozone Developers, Currently, we have two security fixes ([1], [2]) that have been completed and pending to be released. [1] affects only 1.4.1 since 2.0.0 contains this fix, but [2] affects 1.4.1 and 2.0.0 release.
I would like to propose starting two concurrent 1.4.2 and 2.0.1 releases which are focused on security fixes. The focus of this release is simply to fix the security issues. Other improvements / non-security related bug fixes should be released in future releases (e.g. [3]).That being said, there are currently patches that are targeting 1.4.2 [4] and 2.0.1 [5]. Therefore, the plan is to include these existing patches as part of the 1.4.2 and 2.0.1. In summary, for 1.4.2 and 2.0.1 releases I will do the following 1. Backport all the patches targeting 1.4.2 and 2.0.1 to ozone-1.4 and ozone-2.0 branches respectively 2. Backport security patches to ozone-1.4 and ozone-2.0 3. Release 1.4.2 and 2.0.1 based on these patches The target completion time is within one month or less. Therefore, non-critical patches or bug fixes should hold until the next 2.1.0 release. Thanks for your understanding. However, if any community members feel strongly about patches to include in 1.4.2 or 2.0.1 please let me know and I will review in case-by-case basis. I will start the backporting the patches next week and will hopefully release initial RC by end of next week. All feedback is welcome. Regards, Ivan Andika [1] Improve OM decommission check <https://issues.apache.org/jira/browse/HDDS-12646> [2] [Snapshot] Add ACL check regression tests for snapshot operations <https://issues.apache.org/jira/browse/HDDS-12958> [3] Ozone 2.1.0 release thread <https://lists.apache.org/thread/mf9f1plo1o5wj0483pyqsls5ryk6xd4p> [4] Ozone 1.4.2 patches <https://issues.apache.org/jira/browse/HDDS-12082?jql=project%20%3D%20HDDS%20AND%20(cf%5B12310320%5D%20%3D%201.4.2%20OR%20fixVersion%20%3D%201.4.2)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC> [5] Ozone 2.0.1 patches <https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20(cf%5B12310320%5D%20%3D%202.0.1%20OR%20fixVersion%20%3D%202.0.1)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>
