Re: Cutting Ozone 1.3.1

2023-03-14 Thread Kaijie Chen
+1, sound good I would like to propose two more fixes to the list. A FS contract bug caused by HDDS-7253 is fixed by them. https://issues.apache.org/jira/browse/HDDS-7871 https://issues.apache.org/jira/browse/HDDS-7991 Best, Kaijie On Tue, 14 Mar 2023 14:52:38 +0800 Ritesh Shukla wrote

Re: Cutting Ozone 1.3.1

2023-03-14 Thread Kota Uenishi
Hi, +1 (non-binding) from me. I'd also like to have HDDS-7755 included in the release. It's a tiny fix, but fixed severe hang in our cluster, which was the original source of HDDS-7701. We already deployed it to our cluster with our internal distribution by cherry-pick [1], but we'd appreciate a

Joining Ozone slack channel

2023-03-14 Thread Miguel Ángel Fernández Fernández
Hello team, I'm trying to get started with Ozone and I have some basic questions about the Java API. I think it would be more correct to ask them in the community Slack, but access is limited. Would it be possible to get an invite to the Ozone Slack channel? Best regards, Miguel Ángel

Re: Cutting Ozone 1.3.1

2023-03-14 Thread Siddharth Wagle
+1 for 1.3.1 with critical fixes. Best, Sid On Tue, Mar 14, 2023 at 12:53 AM Kota Uenishi wrote: > Hi, > > +1 (non-binding) from me. > > I'd also like to have HDDS-7755 included in the release. It's a tiny > fix, but fixed severe hang in our cluster, which was the original > source of HDDS-7701

Re: Joining Ozone slack channel

2023-03-14 Thread Arpit Agarwal
Hi Miguel, I have invited you. You should get a separate email from Slack. Best, Arpit > On Mar 14, 2023, at 1:04 AM, Miguel Ángel Fernández Fernández > wrote: > > Hello team, > > I'm trying to get started with Ozone and I have some basic questions about > the Java API. I think it would be m

Re: Cutting Ozone 1.3.1

2023-03-14 Thread Ethan Rose
+1 for a patch release with all the fixes previously mentioned. In addition, these bugs related to FSO deletion were fixed since 1.3.0 and should be added: HDDS-7541 HDDS-7592 On Tue, Mar 14, 2023 at 7:53 AM Siddharth Wagle wrote: > +1 for 1.3.1 with critical fixes. > > Best, > Sid > > On Tue, M

Re: Cutting Ozone 1.3.1

2023-03-14 Thread Ritesh Shukla
I recommend adding the 1.3.1 version to the target version field (sample: https://issues.apache.org/jira/browse/HDDS-8142) for the Jiras that should be part of 1.3.1 We can review the list in the next community syncs. The planned date, for now, is set for this month's end. Regards, Ritesh On Tue,

Re: Cutting Ozone 1.3.1

2023-03-14 Thread Ayush Saxena
+1, Sounds good to me. -Ayush On Wed, 15 Mar 2023 at 03:01, Ritesh Shukla wrote: > I recommend adding the 1.3.1 version to the target version field (sample: > https://issues.apache.org/jira/browse/HDDS-8142) for the Jiras that should > be part of 1.3.1 > We can review the list in the next commu