I'm also +1 doing this on trunk with the request that we try to break the work up into small chunks.
(In case it helps: Sometimes I'll develop on a private feature branch just to determine what the "small chunks" are, then re-do the work with small incremental PRs on trunk) On Wed, Aug 19, 2026 at 8:15 PM Cheng Pan <[email protected]> wrote: > +1 for developing on trunk directly. > > > Hadoop 3.6.0 release towards the end of the year > > Hadoop 3.2.0 released in Jan, 2019 > Hadoop 3.3.0 released in Jul, 2020 > Hadoop 3.4.0 released in Mar, 2024 > Hadoop 3.5.0 released in Mar, 2026 > > This expectation may be overly optimistic, but I’m big +1 for more > frequently releases. > > One question, is there any docs for IPv6 testing infra setup? > And how can we setup IPv6-only and dual-stack CI pipelines / local dev env > (via docker)? > > Thanks, > Cheng Pan > > > > > On Aug 20, 2026, at 01:50, Wei-Chiu Chuang <[email protected]> wrote: > > > > Note: I expect the scope is limited to Hadoop Common and HDFS. The cloud > > connectors are not my area of expertise and I'd like to leave that to > > someone more experienced. > > > > On Tue, Aug 18, 2026 at 10:18 PM Shilun Fan <[email protected]> > wrote: > > > >> +1. I support developing the IPv6 changes directly on trunk. A separate > >> feature branch seems unnecessary, especially if the work is split into > >> small, reviewable patches. Targeting Hadoop 3.6.0 toward the end of the > >> year sounds reasonable to me. > >> > >> Best, > >> Shilun Fan > >> > >> On 2026/08/19 05:09:57 Wei-Chiu Chuang wrote: > >>> Would anyone object to developing this in the trunk branch? Given that > >>> there's unlikely any minor releases before the completion of this > >> project, > >>> keep the IPv6 development in a feature branch seems like overkill. > >>> > >>> Let's shoot for Hadoop 3.6.0 release towards the end of the year? > >>> > >>> On Tue, Aug 18, 2026 at 2:26 PM Siyao Meng <[email protected]> wrote: > >>> > >>>> Hi Hadoop community, > >>>> > >>>> We would like to revive IPv6 support work in Hadoop. The immediate > >> goal is > >>>> to address gaps in hadoop-common, hadoop-auth and hadoop-hdfs-client, > >>>> so that IPv6 support in some downstream projects (such as Ozone) can > be > >>>> unblocked, which we estimated would take ~6 commits in hadoop. > >>>> > >>>> We plan to revisit the earlier work and turn the applicable parts into > >>>> small, > >>>> reviewable changes. The main areas would include address parsing and > >>>> formatting, networking, utilities, and test coverage for IPv4, > >> dual-stack, > >>>> and IPv6-only environments. > >>>> > >>>> Feature branches HADOOP-11890 > >>>> <https://github.com/apache/hadoop/compare/HADOOP-11890> and > >> HADOOP-17800 > >>>> <https://github.com/apache/hadoop/compare/HADOOP-17800> look too > >> outdated > >>>> to work on or to be merged to trunk. Therefore, we will not work on > >> either > >>>> feature > >>>> branch. But we might harvest useful bits from either and put that on > >> trunk. > >>>> > >>>> After the relevant changes are merged and validated, downstream > >> projects > >>>> will also need a Hadoop release that includes them. We would discuss > >> and > >>>> plan for that release after the changes are merged. > >>>> > >>>> Feedback on the proposed scope and approach would be appreciated. > >> Please > >>>> also let us know about any related work we should coordinate with, or > >> if > >>>> you would like to contribute or review patches. > >>>> > >>>> ref: https://issues.apache.org/jira/browse/HADOOP-11890 > >>>> > >>>> Thanks, > >>>> Siyao > >>>> Hadoop committer, Ozone PMC member and committer > >>>> On behalf of Ozone PMC > >>>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > >
