Thanks a lot for driving this Wei-Chiu, I'm +1 for deprecating legacy
buckets and o3fs as well. The release plan will need to specify how these
deprecations are implemented and what the impacts will be. For example,
legacy buckets will likely remain readable and writable but creation of new
ones will be blocked. This will have impacts on clients older than version
1.2.0.

Other ideas to consider for a major release:

   - Removing STAND_ALONE replication type (it should be the same as RATIS
   1): HDDS-6218 <https://issues.apache.org/jira/browse/HDDS-6218>
   - CLI cleanup such that all subcommands and flags use kebab-case and
   double dash for long options.
   -  This is a more involved project that we might not have time for.
      Ideally all current non-compliant commands would still work but remain
      hidden in help messages.
      - We would need an enforcement plan going forward to make sure new
      CLI options remain consistent. CI can get us part of the way
there but some
      sort of manual guideline document would also need to be drafted and
      enforced by reviewers.

Regarding proto2 to proto3 migration, Pifta had some ideas in the last
community sync that this may not actually be too complicated and we could
maintain wire compatibility with proto2 clients even if the server is using
proto3. I haven't done any research in this area yet so others can fill in
details if they are aware.

Given this is a major release I would like to see us move towards proper
change logs and release notes in the published announcement instead of the
haiku/picture thing, something I also lamented about in the new website
proposal
<https://issues.apache.org/jira/secure/attachment/13062569/Improving%20the%20Apache%20Ozone%20Website.pdf>.
We can consider that practice "deprecated" too ; )

A new website debut with 2.0 would be great in theory but unfortunately our
docs contributions remain almost zero despite the framework being live for
over 6 months now, so that seems unlikely. I do have plans to take on the
homepage and community sections soon but going forward I can't write 200+
pages of technical docs on my own:

> $ ./progress.sh
> Total pages: 203
> ------------
> Complete pages: 1
> ------------
> Incomplete pages: 202


Ethan

On Wed, Aug 28, 2024 at 11:42 AM Wei-Chiu Chuang <weic...@apache.org> wrote:

> We will keep OBS for sure.
>
> I'm coming up with a release plan. Will share it shortly.
>
> On Tue, Aug 27, 2024 at 11:50 PM Kohei Sugihara <ksugih...@preferred.jp>
> wrote:
>
> > Hi, all
> >
> > > I'd also like to propose to deprecate
> > > LEGACY bucket type
> >
> > Can we keep using the OBS bucket type after the deprecation?
> >
> > 2024年8月28日(水) 8:32 Wei-Chiu Chuang <weic...@apache.org>:
> >
> > > I'd also like to propose to deprecate
> > >
> > > LEGACY bucket type
> > > O3fs file system
> > > IIRC we're still testing Hadoop 3.1 and 3.2 runtime. Can we drop it
> too?
> > >
> > > Anything else?
> > >
> > > On Sun, Aug 25, 2024 at 11:12 PM Guo Hao <guohao1...@apache.org>
> wrote:
> > >
> > > > +1 for Ozone 2.0
> > > >
> > > >
> > > > At 2024-08-24 01:48:38, "Tsz Wo Sze" <szets...@gmail.com> wrote:
> > > > >+1 for Ozone 2.0
> > > > >
> > > > >> (1) I want to drop Hadoop2 support.
> > > > >
> > > > >It would be great if we can also replace proto 2 with proto 3.
> > However,
> > > > it
> > > > >will take some time for the replacement.  It probably has to wait
> till
> > > > >Ozone 3.0.  Hopefully, it won't be 4 more years.
> > > > >
> > > > >@Wei-Chiu Chuang <weic...@apache.org> , thanks a lot for starting
> the
> > > > >discussion!
> > > > >
> > > > >Tsz-Wo
> > > > >
> > > > >
> > > > >On Thu, Aug 22, 2024 at 7:59 PM Wei-Chiu Chuang <weic...@apache.org
> >
> > > > wrote:
> > > > >
> > > > >> There's also Website v2 that's been cooking for quite a while now.
> > > > >> HDDS-9225
> > > > >> <https://issues.apache.org/jira/browse/HDDS-9225>
> > > > >> Good opportunity for optics.
> > > > >>
> > > > >> On Thu, Aug 22, 2024 at 4:19 PM Yi-Sheng Lien <yish...@apache.org
> >
> > > > wrote:
> > > > >>
> > > > >> > +1
> > > > >> >
> > > > >> > Wei-Chiu Chuang <weic...@cloudera.com.invalid> 於 2024年8月23日 週五
> > > 上午6:31
> > > > >> 寫道:
> > > > >> >
> > > > >> > > Hi,
> > > > >> > > I want to throw out another idea: we should be calling it 2.0
> > > > instead.
> > > > >> > >
> > > > >> > > Reason being:
> > > > >> > > (1) I want to drop Hadoop2 support.
> > > > >> > > (2) Ozone 1.0 was exactly 4 years ago. In many ways, its
> > maturity
> > > > and
> > > > >> > > functionalities have changed so much.
> > > > >> > > (3) The HBase support is a significant change.
> > > > >> > > (4) While Snapshot support was added in 1.4.0, we
> significantly
> > > > >> enhanced
> > > > >> > it
> > > > >> > > in the coming release.
> > > > >> > > (5) JDK 17 support also signifies another great milestone.
> > > > >> > > (6) Recon UI went through a major revamp and looks very
> > different
> > > > now.
> > > > >> > >
> > > > >> > > On Thu, Aug 22, 2024 at 12:44 PM Wei-Chiu Chuang <
> > > > weic...@apache.org>
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > Oh actually I forgot to mention:
> > > > >> > > > What about dropping Hadoop2 support? The last Hadoop2
> release
> > > > 2.10.2
> > > > >> > was
> > > > >> > > > two years ago and I am not sure who else is using Hadoop 2
> at
> > > all.
> > > > >> > > > Dropping it will simplify our code, making it easier to
> > > maintain.
> > > > >> > > >
> > > > >> > > > On Thu, Aug 22, 2024 at 11:55 AM Wei-Chiu Chuang <
> > > > weic...@apache.org
> > > > >> >
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > >> Hi community,
> > > > >> > > >>
> > > > >> > > >> I’d like to initiate a discussion about the 1.5.0 release.
> > > There
> > > > >> have
> > > > >> > > >> been significant changes since 1.4.0 (January 2024) with
> > 1,130
> > > > >> commits
> > > > >> > > >> <
> > https://github.com/apache/ozone/compare/ozone-1.4.0...master>
> > > > >> added
> > > > >> > to
> > > > >> > > >> the git history.
> > > > >> > > >>
> > > > >> > > >> I think it’s a good time to start planning for the next
> minor
> > > > >> release.
> > > > >> > > >> Wouldn't it be great if we could announce the release of
> > 1.5.0
> > > at
> > > > >> this
> > > > >> > > >> year's CommunityOverCode conference?
> > > > >> > > >>
> > > > >> > > >> Some of the major features I’m excited to see included are:
> > > > >> > > >> * HBase support HDDS-7593
> > > > >> > > >> <https://issues.apache.org/jira/browse/HDDS-7593>
> > > > >> > > >> * Snapshot support phase 2 HDDS-8544
> > > > >> > > >> <https://issues.apache.org/jira/browse/HDDS-8544>
> > > > >> > > >> * JDK17 support HDDS-8246
> > > > >> > > >> <https://issues.apache.org/jira/browse/HDDS-8246>
> > > > >> > > >>
> > > > >> > > >> Improvements
> > > > >> > > >> * Recon UI HDDS-11153 <
> > > > >> > https://issues.apache.org/jira/browse/HDDS-11153
> > > > >> > > >
> > > > >> > > >> * CVE updates
> > > > >> > > >>
> > > > >> > > >> I'm sure there's more to look forward to, and that makes me
> > > even
> > > > >> more
> > > > >> > > >> excited!
> > > > >> > > >>
> > > > >> > > >> Best,
> > > > >> > > >> Weichiu
> > > > >> > > >>
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> >
> > --
> > Kohei Sugihara, Engineer
> > Preferred Networks, Inc.
> >
>

Reply via email to