+1 for a 1.4.0 release. We had hoped for a 1.3.1 release but it looks like that never gained the momentum it needed. It would be good to hear from devs working on larger features whether or not they would like to target this release. Things like snapshots, cert rotation, hsync, recon improvements etc. From my end I'm planning to have v1of the container scanner done by the end of this month. It would be nice to have in the next release but not essential.
Also worth noting that doing a major release will lock in protos and disk structures as they are on master for compatibility reasons. We have tried to keep the master branch always releasable, but just an FYI to devs working on larger tasks on master right now. Ethan On Wed, Jun 7, 2023 at 1:44 AM Sammi Chen <sammic...@apache.org> wrote: > Dear Ozone Devs, > > It's been almost 5 month since the last major 1.3.0 release in Dec 2022. > > In the past 5 month, there have been a lot of issues fixed and improvements > made, together with new features, like httpFs, scm decommission, Recon new > functions, snapshot, EC balancer support, the the coming symmetric block > token and certificate rotation, etc. > > So far, there are already 733 JIRAs resolved on 1.4.0. > > https://issues.apache.org/jira/issues/?jql=project+%3D+HDDS+and+fixVersion+%3D+1.4.0 > > Usually it will take months to do a major release. So I propose to start > the discussion of 1.4.0 now, things like which features should be involved > in this release. > > And this release doesn't have a Release Manager yet. Welcome > anyone(Comitters or PMCs, for it requires some privileges on Apache > facilities to do the release) to volunteer to be the RM of 1.4.0. > > > Regards, > Sammi >
