You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by Masatake Iwasaki <iw...@oss.nttdata.com> on 2022/07/11 01:12:18 UTC
Re: [DISCUSS] Hadoop 3.2.4 release
I'm going to cut branch-3.2.4 today.
If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
3.2.4 can be released first.
Thanks,
Masatake Iwasaki
On 2022/05/10 0:02, Masatake Iwasaki wrote:
> Hi team,
>
> Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
> of Hadoop 3.2.3 published to Maven turned out to be broken
> due to issue of the release process.
>
> In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was created[1].
> Migration from log4j to reload4j is one of the major issues.
>
> I would like to cut RC of 3.2.4 soon after 3.3.3 release.
> I volunteer to take a release manager role as done for 3.2.3.
>
> [1] https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
>
> Thanks,
> Masatake Iwasaki
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
Hi committers,
I created branch-3.2.4.
Please set the value of "Fix versions/s" field to 3.2.5 on JIRA issue
if the fix is committed to branch-3.2 and not cherry-picked to branch-3.2.4.
Thanks,
Masatake Iwasaki
On 2022/07/11 13:21, Akira Ajisaka wrote:
> Thank you Masatake for proceeding the release process.
>
> -Akira
>
> On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> I'm going to cut branch-3.2.4 today.
>> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
>> 3.2.4 can be released first.
>>
>> Thanks,
>> Masatake Iwasaki
>>
>> On 2022/05/10 0:02, Masatake Iwasaki wrote:
>>> Hi team,
>>>
>>> Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
>>> of Hadoop 3.2.3 published to Maven turned out to be broken
>>> due to issue of the release process.
>>>
>>> In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
>> created[1].
>>> Migration from log4j to reload4j is one of the major issues.
>>>
>>> I would like to cut RC of 3.2.4 soon after 3.3.3 release.
>>> I volunteer to take a release manager role as done for 3.2.3.
>>>
>>> [1]
>> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
Hi committers,
I created branch-3.2.4.
Please set the value of "Fix versions/s" field to 3.2.5 on JIRA issue
if the fix is committed to branch-3.2 and not cherry-picked to branch-3.2.4.
Thanks,
Masatake Iwasaki
On 2022/07/11 13:21, Akira Ajisaka wrote:
> Thank you Masatake for proceeding the release process.
>
> -Akira
>
> On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> I'm going to cut branch-3.2.4 today.
>> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
>> 3.2.4 can be released first.
>>
>> Thanks,
>> Masatake Iwasaki
>>
>> On 2022/05/10 0:02, Masatake Iwasaki wrote:
>>> Hi team,
>>>
>>> Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
>>> of Hadoop 3.2.3 published to Maven turned out to be broken
>>> due to issue of the release process.
>>>
>>> In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
>> created[1].
>>> Migration from log4j to reload4j is one of the major issues.
>>>
>>> I would like to cut RC of 3.2.4 soon after 3.3.3 release.
>>> I volunteer to take a release manager role as done for 3.2.3.
>>>
>>> [1]
>> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
Hi committers,
I created branch-3.2.4.
Please set the value of "Fix versions/s" field to 3.2.5 on JIRA issue
if the fix is committed to branch-3.2 and not cherry-picked to branch-3.2.4.
Thanks,
Masatake Iwasaki
On 2022/07/11 13:21, Akira Ajisaka wrote:
> Thank you Masatake for proceeding the release process.
>
> -Akira
>
> On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> I'm going to cut branch-3.2.4 today.
>> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
>> 3.2.4 can be released first.
>>
>> Thanks,
>> Masatake Iwasaki
>>
>> On 2022/05/10 0:02, Masatake Iwasaki wrote:
>>> Hi team,
>>>
>>> Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
>>> of Hadoop 3.2.3 published to Maven turned out to be broken
>>> due to issue of the release process.
>>>
>>> In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
>> created[1].
>>> Migration from log4j to reload4j is one of the major issues.
>>>
>>> I would like to cut RC of 3.2.4 soon after 3.3.3 release.
>>> I volunteer to take a release manager role as done for 3.2.3.
>>>
>>> [1]
>> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
Hi committers,
I created branch-3.2.4.
Please set the value of "Fix versions/s" field to 3.2.5 on JIRA issue
if the fix is committed to branch-3.2 and not cherry-picked to branch-3.2.4.
Thanks,
Masatake Iwasaki
On 2022/07/11 13:21, Akira Ajisaka wrote:
> Thank you Masatake for proceeding the release process.
>
> -Akira
>
> On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> I'm going to cut branch-3.2.4 today.
>> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
>> 3.2.4 can be released first.
>>
>> Thanks,
>> Masatake Iwasaki
>>
>> On 2022/05/10 0:02, Masatake Iwasaki wrote:
>>> Hi team,
>>>
>>> Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
>>> of Hadoop 3.2.3 published to Maven turned out to be broken
>>> due to issue of the release process.
>>>
>>> In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
>> created[1].
>>> Migration from log4j to reload4j is one of the major issues.
>>>
>>> I would like to cut RC of 3.2.4 soon after 3.3.3 release.
>>> I volunteer to take a release manager role as done for 3.2.3.
>>>
>>> [1]
>> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
>>>
>>> Thanks,
>>> Masatake Iwasaki
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Akira Ajisaka <aa...@apache.org>.
Thank you Masatake for proceeding the release process.
-Akira
On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> I'm going to cut branch-3.2.4 today.
> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
> 3.2.4 can be released first.
>
> Thanks,
> Masatake Iwasaki
>
> On 2022/05/10 0:02, Masatake Iwasaki wrote:
> > Hi team,
> >
> > Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
> > of Hadoop 3.2.3 published to Maven turned out to be broken
> > due to issue of the release process.
> >
> > In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
> created[1].
> > Migration from log4j to reload4j is one of the major issues.
> >
> > I would like to cut RC of 3.2.4 soon after 3.3.3 release.
> > I volunteer to take a release manager role as done for 3.2.3.
> >
> > [1]
> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
> >
> > Thanks,
> > Masatake Iwasaki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Akira Ajisaka <aa...@apache.org>.
Thank you Masatake for proceeding the release process.
-Akira
On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> I'm going to cut branch-3.2.4 today.
> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
> 3.2.4 can be released first.
>
> Thanks,
> Masatake Iwasaki
>
> On 2022/05/10 0:02, Masatake Iwasaki wrote:
> > Hi team,
> >
> > Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
> > of Hadoop 3.2.3 published to Maven turned out to be broken
> > due to issue of the release process.
> >
> > In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
> created[1].
> > Migration from log4j to reload4j is one of the major issues.
> >
> > I would like to cut RC of 3.2.4 soon after 3.3.3 release.
> > I volunteer to take a release manager role as done for 3.2.3.
> >
> > [1]
> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
> >
> > Thanks,
> > Masatake Iwasaki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Akira Ajisaka <aa...@apache.org>.
Thank you Masatake for proceeding the release process.
-Akira
On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> I'm going to cut branch-3.2.4 today.
> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
> 3.2.4 can be released first.
>
> Thanks,
> Masatake Iwasaki
>
> On 2022/05/10 0:02, Masatake Iwasaki wrote:
> > Hi team,
> >
> > Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
> > of Hadoop 3.2.3 published to Maven turned out to be broken
> > due to issue of the release process.
> >
> > In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
> created[1].
> > Migration from log4j to reload4j is one of the major issues.
> >
> > I would like to cut RC of 3.2.4 soon after 3.3.3 release.
> > I volunteer to take a release manager role as done for 3.2.3.
> >
> > [1]
> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
> >
> > Thanks,
> > Masatake Iwasaki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [DISCUSS] Hadoop 3.2.4 release
Posted by Akira Ajisaka <aa...@apache.org>.
Thank you Masatake for proceeding the release process.
-Akira
On Mon, Jul 11, 2022 at 10:12 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> I'm going to cut branch-3.2.4 today.
> If we need more time for 3.3.4 to fix the issue around HADOOP-18033,
> 3.2.4 can be released first.
>
> Thanks,
> Masatake Iwasaki
>
> On 2022/05/10 0:02, Masatake Iwasaki wrote:
> > Hi team,
> >
> > Shaded client artifacts (hadoop-client-api and hadoop-client-runtime)
> > of Hadoop 3.2.3 published to Maven turned out to be broken
> > due to issue of the release process.
> >
> > In addition, we have enough fixes on branch-3.2 after branch-3.2.3 was
> created[1].
> > Migration from log4j to reload4j is one of the major issues.
> >
> > I would like to cut RC of 3.2.4 soon after 3.3.3 release.
> > I volunteer to take a release manager role as done for 3.2.3.
> >
> > [1]
> https://issues.apache.org/jira/issues/?filter=12350757&jql=project%20in%20(YARN%2C%20HDFS%2C%20HADOOP%2C%20MAPREDUCE)%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%203.2.4
> >
> > Thanks,
> > Masatake Iwasaki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>