You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ozone.apache.org by Wei-Chiu Chuang <we...@apache.org> on 2025/04/10 18:45:14 UTC

[DISCUSS] Apache Ozone 2.0.1

As we wind down the 2.0.0 release activity, I want to start the
conversation on the next milestone.

It was just three weeks of commits, but we've accumulated 124 commits
<https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20HDDS%20AND%20fixVersion%20in%20(2.1.0)%20AND%20fixVersion%20not%20in%20(2.0.0)%20AND%20status%20in%20(Resolved)%20ORDER%20BY%20priority%20DESC&startIndex=50>
in the master branch already. I would like to make regular releases
where the diff between each release is within a reasonable delta. That
makes the regression easier to track and vulnerable dependencies can be
updated quicker.

What do folks think? I'd like to propose a regular, monthly release, and
keep the vote process lightweight. Even a monthly snapshot release would be
useful for application developers to adopt.

Cheers!
Weichiu

Re: [DISCUSS] Apache Ozone 2.0.1

Posted by Wei-Chiu Chuang <we...@cloudera.com.INVALID>.
>
> How about using 2.1.0 instead?
>

We need to have a discussion thread for 2.1.0 roadmap items as well.
Right now I see several near time features that make a good 2.1.0 release.

(1) S3 lifecycle management.
(2) Short Circuit Read.
(3) Diskbalancer.

and maybe Trino support and Listener OM?

Re: [DISCUSS] Apache Ozone 2.0.1

Posted by Tsz-Wo Nicholas Sze <sz...@gmail.com>.
> ... we've accumulated 124 commits ...

For 2.0.1, we should select only bug fixes and improvements but not new
features since it is a maintenance release.  There are probably new
features in these commits.  How about using 2.1.0 instead?  If there is a
need, we could cherry-pick and release 2.0.1 later on.

> How about a quarterly or 3-4 times event driven releases in one year?

Time based approach usually works better then event driven -- it is easier
to answer a yes/no ( in-or-out for the next release ) question for each
JIRA than selecting a time to roll a new release.

Tsz-Wo



On Thu, Apr 10, 2025 at 8:06 PM Sammi Chen <sa...@apache.org> wrote:

> Wei-Chiu,  Thanks for raising this topic.
>
> It would be great if the latest updates of Ozone can be released timely, so
> Ozone users can benefit from that.
>
> I'm just a little worried about whether we have enough resouce to support
> monthly release and guarantee the quality.
>
> How about a quarterly or 3-4 times event driven releases in one year?
>
> Bests,
> Sammi
>
>
>
> On Fri, 11 Apr 2025 at 02:45, Wei-Chiu Chuang <we...@apache.org> wrote:
>
> > As we wind down the 2.0.0 release activity, I want to start the
> > conversation on the next milestone.
> >
> > It was just three weeks of commits, but we've accumulated 124 commits
> > <
> >
> https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20HDDS%20AND%20fixVersion%20in%20(2.1.0)%20AND%20fixVersion%20not%20in%20(2.0.0)%20AND%20status%20in%20(Resolved)%20ORDER%20BY%20priority%20DESC&startIndex=50
> > >
> > in the master branch already. I would like to make regular releases
> > where the diff between each release is within a reasonable delta. That
> > makes the regression easier to track and vulnerable dependencies can be
> > updated quicker.
> >
> > What do folks think? I'd like to propose a regular, monthly release, and
> > keep the vote process lightweight. Even a monthly snapshot release would
> be
> > useful for application developers to adopt.
> >
> > Cheers!
> > Weichiu
> >
>

Re: [DISCUSS] Apache Ozone 2.0.1

Posted by Sammi Chen <sa...@apache.org>.
Wei-Chiu,  Thanks for raising this topic.

It would be great if the latest updates of Ozone can be released timely, so
Ozone users can benefit from that.

I'm just a little worried about whether we have enough resouce to support
monthly release and guarantee the quality.

How about a quarterly or 3-4 times event driven releases in one year?

Bests,
Sammi



On Fri, 11 Apr 2025 at 02:45, Wei-Chiu Chuang <we...@apache.org> wrote:

> As we wind down the 2.0.0 release activity, I want to start the
> conversation on the next milestone.
>
> It was just three weeks of commits, but we've accumulated 124 commits
> <
> https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20HDDS%20AND%20fixVersion%20in%20(2.1.0)%20AND%20fixVersion%20not%20in%20(2.0.0)%20AND%20status%20in%20(Resolved)%20ORDER%20BY%20priority%20DESC&startIndex=50
> >
> in the master branch already. I would like to make regular releases
> where the diff between each release is within a reasonable delta. That
> makes the regression easier to track and vulnerable dependencies can be
> updated quicker.
>
> What do folks think? I'd like to propose a regular, monthly release, and
> keep the vote process lightweight. Even a monthly snapshot release would be
> useful for application developers to adopt.
>
> Cheers!
> Weichiu
>