Hi Ozone developers, I would like to propose preparing the next release based on master instead of the ozone-1.4 branch.
Unlike with previous releases, we started regularly backporting fixes to ozone-1.4 soon after Ozone 1.4.0 was released. Currently 99 commits are present on the branch on top of 1.4.0. There are 11 further issues targeted at 1.4.1 but not yet backported. However, there are 526 additional commits on master, not (yet) targeted at 1.4.1. (excludes 3 reverts, 2 addendums and 2 post-release commits) There were ~60 dependency version updates and ~165 changes specific to tests and CI. We might consider skipping these, but that would make backporting the rest much more difficult due to conflicts. The majority of the remaining ~300 commits are fixes/improvements important at least to some users/developers (e.g. the ones who reported and/or worked on the issues). No big features have been introduced since 1.4.0, so I would expect a release from the master branch to be stable. Such features are being developed on separate branches. This also makes it possible to still call the next release 1.4.1. Some changes that may need special consideration (e.g. revert from the release branch or additional testing/validation): - HDDS-8113. Remove Hadoop 2.7 compatibility hack - HDDS-815. Rename HDDS config keys prefixed with dfs + HDDS-10331. Rename Java constants of ex-DFS config keys - HDDS-7791. Support key ownership - HDDS-9648. Create API to fetch info about a single datanode - HDDS-9343. Shift sortDatanodes logic to OM (7 sub-tasks, 2 still to be done) - HDDS-10538. Replace GSON with Jackson (6 sub-tasks, 2 still to be done) Please let me know your thoughts. thanks, Attila --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org For additional commands, e-mail: dev-h...@ozone.apache.org
