Hi mapreduce/yarn/common/hdfs-devs,
As of now, we have all blockers done for 3.1.0 release [1]. The release is
running behind schedule due to a few security-related issues. Because of
this and since branch-3.1 is cut 5 weeks before on Feb 8, trunk 3.2 is
already diverging. There're 64 commits in t
I see one new feature: https://issues.apache.org/jira/browse/YARN-7626: Allow
regular expression matching in container-executor.cfg for devices and named
docker volumes mount.
There are 21 sub-tasks. There are three feature-type JIRAs in those -
https://issues.apache.org/jira/browse/YARN-7972,
Thanks for sharing your thoughts.
We have done build and single node cluster deploy / test for the latest
trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). Since there
are no objections, so I will go ahead to do the branch replace.
Since we don't have force push permission to release
+1 for resetting branch-3.1.
Thanks,
Akira
On 2018/03/18 12:51, Wangda Tan wrote:
Thanks for sharing your thoughts.
We have done build and single node cluster deploy / test for the latest
trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). Since there
are no objections, so I will go
Thanks Akira for the additional vote,
With help from Apache Infra Team (Daniel Takamori), we just reset
branch-3.1 to trunk (SHA: 49c747ab187d0650143205ba57ca19607ec4c6bd). Will
update JIRA fix version shortly.
- Wangda
On Sun, Mar 18, 2018 at 6:10 PM, Akira Ajisaka
wrote:
> +1 for resetting b
Done JIRA fix version update:
Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes
(which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd)
YARN-8002. Support NOT_SELF and ALL namespace types for allocation tag.
(Weiwe
i Yang via wangda)
HADOOP-15262. Aliyu
Thanks Wangda.
On 3/19/18, 11:38 AM, "Wangda Tan" wrote:
Done JIRA fix version update:
Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes
(which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd)
YARN-8002. Support NOT_SELF and ALL
I just pulled the latest from branch-3.1 and noticed that now that it was
reset to trunk, the version in the pom.xml files is 3.2.0-SNAPSHOT instead
of 3.1.0-SNAPSHOT. Is somebody going to submit a new commit to change this
version back to 3.1.0-SNAPSHOT in this branch?
Thank you,
Jonathan
On Mon
Thanks for reporting this.
It's straight forward. Done, commit pushed.
Thanks
+Vinod
> On Mar 19, 2018, at 2:54 PM, Jonathan Kelly wrote:
>
> I just pulled the latest from branch-3.1 and noticed that now that it was
> reset to trunk, the version in the pom.xml files is 3.2.0-SNAPSHOT instead
>
Thank you!
On Mon, Mar 19, 2018 at 3:34 PM Vinod Kumar Vavilapalli
wrote:
> Thanks for reporting this.
>
> It's straight forward. Done, commit pushed.
>
> Thanks
> +Vinod
>
> > On Mar 19, 2018, at 2:54 PM, Jonathan Kelly
> wrote:
> >
> > I just pulled the latest from branch-3.1 and noticed that
ranch-3.1 to trunk before release.
Done JIRA fix version update:
Moved all JIRAs with fixVersion = 3.2.0 to 3.1.0 except following few fixes
(which committed after 49c747ab187d0650143205ba57ca19607ec4c6bd)
YARN-8002. Support NOT_SELF and ALL namespace types for allocation tag.
(Weiwe
i Yan
arch 20, 2018 2:38 AM
> To: Akira Ajisaka
> Cc: Vinod Kumar Vavilapalli ;
> yarn-dev@hadoop.apache.org; Hdfs-dev ;
> common-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
> Subject: Re: About reset branch-3.1 to trunk before release.
>
> Done JIRA fix version update:
>
12 matches
Mail list logo
