Thanks @Symious for your feedback. Every time we release a new version, in addition to releasing new features, it is more important to fix some bugs from the previous version. In 1.2 we released new features (SCM HA, FSO, Non rolling upgrades) and we also fixed some bugs this time. This also in order to provide a more stable release for all users.
Maybe we can't wait for all the new features bugs to be fixed before release new ozone version. Because Ozone has new features merged every once in a while. Over time it is possible that Ozone streaming and Merge rocksDB and others will merge, which will also create new bugs. There are always new features, and new features bugs, but that shouldn't affect us release new version. For the new feature released this time, we can solve the bugs in the next release. It's also about getting more people to help us find problems. On Fri, Apr 22, 2022 at 5:00 PM Janus Chow <yiyang0...@gmail.com> wrote: > Thanks @MingChao for bringing this up. > > Looking forward to the release with these new great features. > > But IMHO, since these are quite large changes of the new features, and > some indetectable bugs may need some time and usage to show themselves. > In order to provide a more stable release for all users of Ozone, may be > we can wait a little longer for some fixes? > > Thanks > Symious > > > On 22 Apr 2022, at 4:43 PM, mingchao zhao <captain...@apache.org> wrote: > > > > Dear all, > > > > It has been a few months since the Ozone 1.2.0 & 1.2.1 release, and we > have > > had a > > number of new features (EC）and some optimization(s3gateway) and some > > bug fixes > > for 1.2 that have been merged to master since then. I think this would > be a > > good time > > to work on the Ozone 1.3.0 release. Also, I volunteered to take up the > role > > of the > > Release Manager for this release. > > > > Please let me know what you think. > > > > > > -- > > Thanks & Regards, > > MingChao > >
