In one of the previous emails, Nicholas mentioned that we are planning to roll Ratis release once Duong's verification is done. If the Ratis community is planning to release 3.1 soon, I would like to call the Ozone release as 1.5.0 (based on master), which includes a bunch of key performance optimizations that need a Ratis version bump in Ozone. If some users are still on 1.4.0 and want bug fix release, we can continue making a release of 1.4.1 based on the 1.4.0 branch later. Otherwise, we can continue to put our energy on 1.5.0 to stabilize IMO.
Regards, Uma On Wed, May 8, 2024 at 3:24 PM Ethan Rose <er...@apache.org> wrote: > Doing the next release from master makes sense to me given the increased > focus on bug fixes and stability. I don't think I have a preference on > calling it 1.4.1 or 1.5.0. It might be strange to have an ozone-1.4 branch > and then an ozone-1.4.1 branch that is not based off it, but that's not a > big deal. If 1.4.1 makes more sense from a semver perspective with what is > being delivered then let's use that label. > > Ethan > > On Tue, May 7, 2024 at 10:38 AM Attila Doroszlai <adorosz...@apache.org> > wrote: > > > 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 > > > > >
