Hello dev,
I'm excited to share that the Ozone-1.4 branch is now set up and ready.
Here’s what you need to know:
- Ozone-1.4 Branch: All release-related tasks should now be conducted on
the ozone-1.4 <https://github.com/apache/ozone/tree/ozone-1.4> branch,
tracked in HDDS-9928 <https://issues.apache.org/jira/browse/HDDS-9928>.
- New PRs: New PRs should be directed to the master branch.
- Cherry-Picking to Ozone-1.4: We have HDDS-9929
<https://issues.apache.org/jira/browse/HDDS-9929> to track PRs that need
to be cherry-picked into the Ozone-1.4 branch.
Please ensure to record any such PRs there. Feel free to reach out with
any questions.
Thanks for your continued efforts!
Warm Regards.
--
Yiyang Zhou
Janus Chow <yiyang0...@gmail.com> 于2023年12月13日周三 11:04写道：
> Hello dev,
>
> Thanks @Wei-Chiu Chuang <weic...@apache.org> for the advice.
>
> LGTM to branch out now, if no other comments till tomorrow, I will do
> the branch out and version update then.
>
> For current blockers, they will be cherry-picked to branch-1.4 after
> being fixed.
>
> Warm Regards.
>
> --
> Yiyang Zhou
>
>
> Wei-Chiu Chuang <weic...@apache.org> 于2023年12月13日周三 03:23写道：
>
>> Both are fixed now.
>>
>> I see that master branch is still referring to 1.4.0-SNAPSHOT. I'd
>> recommend to branch out to branch-1.4, update master branch to use
>> 1.5.0-SNAPSHOT, so we can move into code freeze phase, allowing only
>> blocker issues in the branch. And declare all fixed issues in master
>> branch
>> are marked as resolved in 1.5.0.
>>
>> On Mon, Dec 4, 2023 at 12:47 AM Janus Chow <yiyang0...@gmail.com> wrote:
>>
>> > Hi devs,
>> >
>> > @Maxim, thank you for the update.
>> >
>> > Since Datanode write performance degradation is fixed, only two
>> tickets
>> > need to be fixed:
>> >
>> > - https://issues.apache.org/jira/browse/HDDS-9709
>> > - https://issues.apache.org/jira/browse/HDDS-9762
>> >
>> >
>> >
>> > Warm Regards.
>> >
>> > --
>> > Yiyang Zhou
>> >
>> >
>> > Maxim Myskov <maxim.mys...@gmail.com> 于2023年12月4日周一 16:43写道：
>> >
>> > > Hi devs,
>> > >
>> > > HDDS-9817 <https://issues.apache.org/jira/browse/HDDS-9817> was an
>> issue
>> > > of our internal Ozone build. It is now closed (no code changes
>> needed).
>> > >
>> > > > On 1 Dec 2023, at 13:05, Maxim Myskov <maxim.mys...@gmail.com>
>> wrote:
>> > > >
>> > > > Hi devs,
>> > > >
>> > > > We've identified a critical bug that we believe is a blocker for the
>> > > upcoming release. The issue is documented here:
>> > > > * https://issues.apache.org/jira/browse/HDDS-9817 S3 get secret
>> > > endpoint returns 500
>> > > >
>> > > > The issue is about S3 get secret endpoint returning a 500 error,
>> > > causing our clients to face difficulties in generating secret keys.
>> > > > Our team has already initiated efforts to resolve the bug, and we
>> are
>> > > actively working on implementing a fix.
>> > > >
>> > > >
>> > > >> On 27 Nov 2023, at 21:32, Attila Doroszlai <adorosz...@apache.org>
>> > > wrote:
>> > > >>
>> > > >> Hi Yiyang and devs,
>> > > >>
>> > > >> In today's US community sync two other bugs targeted at 1.4.0 were
>> > > >> marked as blocker:
>> > > >>
>> > > >> * HDDS-9709. Intermittent NO_REPLICA_FOUND due to OM pipeline cache
>> > bug
>> > > >> * HDDS-9762. Hadoop s3a protocol does not work with FSO buckets
>> > > >>
>> > > >> The first one should be quick: it already has a patch available,
>> only
>> > > >> needs review.
>> > > >>
>> > > >> The second one still needs to be investigated, any contribution
>> > welcome.
>> > > >>
>> > > >> We also discussed the need to publish a 1.3.1 patch release with
>> the
>> > > >> fix for HDDS-8647, to avoid hitting this bug during upgrade to
>> 1.4.0
>> > > >> (HDDS-8711).
>> > > >>
>> > > >> -Attila
>> > > >>
>> > > >>
>> ---------------------------------------------------------------------
>> > > >> To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
>> > > >> For additional commands, e-mail: dev-h...@ozone.apache.org
>> > > >>
>> > > >
>> > >
>> > >
>> >
>>
>
