I'm thinking of doing a backport of most of the hadoop-aws changes to
branch-3.2, for the next 3.2.x release; they are all self contained and
will benefit many (they will need to cope with the older mockito version,
but I have to deal with that in-house already).

one change is the new openFile() builder API. I'd like to wrap that up with
a little improvement https://issues.apache.org/jira/browse/HADOOP-16759;
That way for all releases with the API, it's consistent.

(that withStatus() feature gives extra performance and ensures that
etag/version can be used to get the explicit version you want.)

On Tue, Jan 7, 2020 at 2:18 AM Akira Ajisaka <aajis...@apache.org> wrote:

> >  I am interested on 3.3 release ..will act as RM .will update the wiki as
> well..
>
> Thanks Brahma for your reply. I'll help you as co-RM.
> We will send announcements (cutting branches, code freeze, and so on) in
> another thread.
>
> Thanks,
> Akira
>
> On Tue, Jan 7, 2020 at 4:32 AM Wangda Tan <wheele...@gmail.com> wrote:
>
> > Hi guys,
> >
> > Thanks for the update and for volunteering to be RM.
> >
> > I just did a quick check:
> > 3.1.4 has 52 patches resolved. (3.1.3 Released on Oct 21)
> > 3.2.2 has 46 patches resolved. (3.2.1 Released on Sep 22)
> > 3.3.0 has .. many patches sitting here so we definitely need a release.
> >
> > If Akira and Brahma you guys can be co-RMs for 3.3.0 that would be great.
> >
> > Hadoop 3.2.1 is released on Sep 22 which is 3+ months ago, and I saw
> > community started to have large prod deployment on 3.2.x, Gabor if you
> have
> > bandwidth to help releases, I think we can do 3.2.2 first then 3.1.4.
> >
> > Thoughts?
> > - Wangda
> >
> > On Mon, Jan 6, 2020 at 5:50 AM Brahma Reddy Battula <bra...@apache.org>
> > wrote:
> >
> >> Thanks Akira for resuming this..
> >>
> >>  I am interested on 3.3 release ..will act as RM .will update the wiki
> as
> >> well..
> >>
> >>
> >>
> >> On Mon, 6 Jan 2020 at 6:08 PM, Gabor Bota <gabor.b...@cloudera.com
> .invalid>
> >> wrote:
> >>
> >>> I'm interested in doing a release of hadoop.
> >>> The version we need an RM is 3.1.3 right? What's the target date for
> >>> that?
> >>>
> >>> Thanks,
> >>> Gabor
> >>>
> >>> On Mon, Jan 6, 2020 at 8:31 AM Akira Ajisaka <aajis...@apache.org>
> >>> wrote:
> >>>
> >>> > Thank you Wangda.
> >>> >
> >>> > Now it's 2020. Let's release Hadoop 3.3.0.
> >>> > I created a wiki page for tracking blocker/critical issues for 3.3.0
> >>> and
> >>> > I'll check the issues in the list.
> >>> >
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.3+Release
> >>> > If you find blocker/critical issues in trunk, please set the target
> >>> version
> >>> > to 3.3.0 for tracking.
> >>> >
> >>> > > We still need RM for 3.3.0 and 3.1.3.
> >>> > I can work as a release manager for 3.3.0. Is there anyone who wants
> >>> to be
> >>> > a RM?
> >>> >
> >>> > Thanks and regards,
> >>> > Akira
> >>> >
> >>> > On Fri, Aug 16, 2019 at 9:28 PM zhankun tang <tangzhan...@gmail.com>
> >>> > wrote:
> >>> >
> >>> > > Thanks Wangda for bring this up!
> >>> > >
> >>> > > I ran the submarine 0.2.0 release before with a lot of help from
> >>> folks
> >>> > > especially Sunil. :D
> >>> > > And this time I would like to help to release the 3.1.4. Thanks!
> >>> > >
> >>> > > BR,
> >>> > > Zhankun
> >>> > >
> >>> > > Hui Fei <feihui.u...@gmail.com>于2019年8月16日 周五下午7:19写道:
> >>> > >
> >>> > > > Hi Wangda,
> >>> > > > Thanks for bringing this up!
> >>> > > > Looking forward to see HDFS 3.x is widely used,but RollingUpgrade
> >>> is a
> >>> > > > problem.
> >>> > > > Hope commiters watch and review these issues, Thanks
> >>> > > > https://issues.apache.org/jira/browse/HDFS-13596
> >>> > > > https://issues.apache.org/jira/browse/HDFS-14396
> >>> > > >
> >>> > > > Wangda Tan <wheele...@gmail.com> 于2019年8月10日周六 上午10:59写道:
> >>> > > >
> >>> > > > > Hi all,
> >>> > > > >
> >>> > > > > Hope this email finds you well
> >>> > > > >
> >>> > > > > I want to hear your thoughts about what should be the release
> >>> plan
> >>> > for
> >>> > > > > 2019.
> >>> > > > >
> >>> > > > > In 2018, we released:
> >>> > > > > - 1 maintenance release of 2.6
> >>> > > > > - 3 maintenance releases of 2.7
> >>> > > > > - 3 maintenance releases of 2.8
> >>> > > > > - 3 releases of 2.9
> >>> > > > > - 4 releases of 3.0
> >>> > > > > - 2 releases of 3.1
> >>> > > > >
> >>> > > > > Total 16 releases in 2018.
> >>> > > > >
> >>> > > > > In 2019, by far we only have two releases:
> >>> > > > > - 1 maintenance release of 3.1
> >>> > > > > - 1 minor release of 3.2.
> >>> > > > >
> >>> > > > > However, the community put a lot of efforts to stabilize
> >>> features of
> >>> > > > > various release branches.
> >>> > > > > There're:
> >>> > > > > - 217 fixed patches in 3.1.3 [1]
> >>> > > > > - 388 fixed patches in 3.2.1 [2]
> >>> > > > > - 1172 fixed patches in 3.3.0 [3] (OMG!)
> >>> > > > >
> >>> > > > > I think it is the time to do maintenance releases of 3.1/3.2
> and
> >>> do a
> >>> > > > minor
> >>> > > > > release for 3.3.0.
> >>> > > > >
> >>> > > > > In addition, I saw community discussion to do a 2.8.6 release
> for
> >>> > > > security
> >>> > > > > fixes.
> >>> > > > >
> >>> > > > > Any other releases? I think there're release plans for Ozone as
> >>> well.
> >>> > > And
> >>> > > > > please add your thoughts.
> >>> > > > >
> >>> > > > > Volunteers welcome! If you have interests to run a release as
> >>> Release
> >>> > > > > Manager (or co-Resource Manager), please respond to this email
> >>> thread
> >>> > > so
> >>> > > > we
> >>> > > > > can coordinate.
> >>> > > > >
> >>> > > > > Thanks,
> >>> > > > > Wangda Tan
> >>> > > > >
> >>> > > > > [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution =
> >>> Fixed
> >>> > > AND
> >>> > > > > fixVersion = 3.1.3
> >>> > > > > [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution =
> >>> Fixed
> >>> > > AND
> >>> > > > > fixVersion = 3.2.1
> >>> > > > > [3] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution =
> >>> Fixed
> >>> > > AND
> >>> > > > > fixVersion = 3.3.0
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >> --
> >>
> >>
> >>
> >> --Brahma Reddy Battula
> >>
> >
>

Reply via email to