Re: [DISCUSS] 1.3.0 release

< > > captain...@apache.org>; > > 发送时间: 2022年7月27日(星期三) 上午10:43 > > 收件人: "dev" > > > 主题: [DISCUSS] 1.3.0 release > > > > > > > > Dear all, > > > > It's been a long time

Re: [DISCUSS] 1.3.0 release

"dev" > < > captain...@apache.org>; > 发送时间: 2022年7月27日(星期三) 上午10:43 > 收件人: "dev" > 主题: [DISCUSS] 1.3.0 release > > > > Dear all, > > It's been a long time since we talked about release in Email and Slack. So > far

??????[DISCUSS] 1.3.0 release

+1 Thx MingChao for this work~ --  -- ??: "dev"

Re: [DISCUSS] 1.3.0 release

+1 Thanks Mingchao. P.S. I'm trying to figure out an issue related to block deleting, and I hope it could be fixed in this release. Best, Kaijie Chen

Re: [DISCUSS] 1.3.0 release

+1, Thanks Mingchao for the initiative -Ayush > On 28-Jul-2022, at 12:52 PM, Sammi Chen wrote: > > 1 > > Thanks Mingchao - To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org For additional commands, e-mail: dev-h...@oz

Re: [DISCUSS] 1.3.0 release

+1 Thanks mingchao for bringing this up again! mingchao zhao 于2022年7月27日周三 10:43写道： > Dear all, > > It's been a long time since we talked about release in Email and Slack. So > far I see that the block tasks listed before are almost complete. > Here are the block tasks we discussed before. > <

Re: [DISCUSS] 1.3.0 release

+1 Thanks Mingchao for leading this effort. Bests, Sammi On Wed, 27 Jul 2022 at 10:43, mingchao zhao wrote: > Dear all, > > It's been a long time since we talked about release in Email and Slack. So > far I see that the block tasks listed before are almost complete. > Here are the block tas

Re: [Internet][DISCUSS] 1.3.0 release

+1. I think we should fix the RocksDB memory leaks so we can increase to version 7 in this release, but those can be cherry-picked on to the branch. On Tue, Jul 26, 2022 at 7:48 PM baoloongmao(毛宝龙) wrote: > +1, thank you. > > > > > > > > > >--回复的邮件信息-- > > mingchao zhao 上

Re：[Internet][DISCUSS] 1.3.0 release

+1, thank you. --回复的邮件信息-- mingchao zhaohttps://the-asf.slack.com/archives/C5RK7PWA1/p1655845645903989?thread_ts=1655801662.600279&cid=C5RK7PWA1>;   Here is the 1.3.0 Release wiki page. ; I thin

[DISCUSS] 1.3.0 release

Dear all, It's been a long time since we talked about release in Email and Slack. So far I see that the block tasks listed before are almost complete. Here are the block tasks we discussed before.

Re: [DISCUSS] 1.3.0 release

Thanks all for the active discussion. At present,The discussion was more in favor of delayed release. The main reason is that: 1. Some features have been merged recently, we need a few weeks to fix bugs, such as EC. 2. Many new features need improvement , such as EC needing Offline Recovery. 3. Th

Re: [DISCUSS] 1.3.0 release

Hi, I also agree with Stephen and Ethan at least in that it is a bit early to cut a new release... I would even consider calling the new release 2.0.0 as so many new things are coming with it, it may be worth something bigger than a minor version bump. But Ethan is right, we have a couple of thin

Re: [DISCUSS] 1.3.0 release

Also a reminder that there is still a merge vote for HDDS-4440 ongoing as well. It may be best to resolve that before discussing a release. On Fri, Apr 22, 2022 at 7:32 AM Ethan Rose wrote: > Hi MingChao, thanks for driving this effort. > > We have a few release blockers on the upgrade side that

Re: [DISCUSS] 1.3.0 release

Hi MingChao, thanks for driving this effort. We have a few release blockers on the upgrade side that need to be resolved before we can release: - SCM HA finalization (I have begun working on this): HDDS-5141 - Onboarding FSO into the upgrade framework (this can start now that EC has been onboarded

Re: [DISCUSS] 1.3.0 release

I think we could mark EC as a [tech preview] feature clearly in this 1.3.0 release. And we could release EC as a completed feature in the next release if possible. At 2022-04-22 20:26:07, "Kota Uenishi" wrote: >I would welcome 1.3 release even without EC available. This is because >a

Re: [DISCUSS] 1.3.0 release

I would welcome 1.3 release even without EC available. This is because a lot of other features and fixes I need in our system. For example, HDDS-5881, HDDS-5461, HDDS-5656, HDDS-5975, HDDS-6321 and such. Delivering them would be very valuable. As RocksDB crash is also happening in our cluster inter

Re: [DISCUSS] 1.3.0 release

I think 1.2.2 sounds like a bug fix version.If we are going to release a new feature version, 1.3.0 would be the proper name. On 星期五, 22 四月 2022 19:13:18 +0800 captain...@apache.org wrote Thanks @Stephen for your feedback. Maybe we can de-emphasize the EC in this version. If EC recov

Re: [DISCUSS] 1.3.0 release

Thanks @Stephen for your feedback. Maybe we can de-emphasize the EC in this version. If EC recovery is completed, it will take until the second half of the year. It's been a little long since the last release. Since last release, FSO, S3gateway, OM, container Balancer have made some optimizations

Re: [DISCUSS] 1.3.0 release

My feeling is that it may be worth waiting until the recovery side of EC is working before releasing. As it stands, EC is not in a usable form - the feature is half done. If we release 1.3.0 now, we cannot state EC is available in it. On Fri, Apr 22, 2022 at 9:43 AM mingchao zhao wrote: > Dear a

Re: [DISCUSS] 1.3.0 release

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 or

Re: [DISCUSS] 1.3.0 release

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 us

[DISCUSS] 1.3.0 release

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,