Re: Apache Hadoop 3.0.1 Release plan
I have reduced the priority for YARN-5742 as we have work around. Also, I have removed target version since we do not have plans to handle this in coming releases. -Rohith Sharma K S On 8 February 2018 at 22:30, Lei Xuwrote: > Hi, Brahma > > Thanks for reminder. YARN-5742 does not look like a blocker to me. I > will create a RC right after HADOOP-14060. > > On Thu, Feb 8, 2018 at 7:35 AM, Kihwal Lee wrote: > > HADOOP-14060 is a blocker. Daryn will add more detail to the jira or to > > this thread. > > > > On Thu, Feb 8, 2018 at 7:01 AM, Brahma Reddy Battula < > brbapa...@gmail.com> > > wrote: > >> > >> Hi Eddy, > >> > >> HDFS-12990 got committed to 3.0.1,can we have RC for 3.0.1 (only > >> YARN-5742 > >> blocker is open ) ? > >> > >> > >> On Sat, Feb 3, 2018 at 12:40 AM, Chris Douglas > >> wrote: > >> > >> > On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwal > >> > > >> > wrote: > >> > > Do you plan to roll an RC with an uncommitted fix? That isn't the > >> > > right > >> > approach. > >> > > >> > The fix will be committed to the release branch. We'll vote on the > >> > release, and if it receives a majority of +1 votes then it becomes > >> > 3.0.1. That's how the PMC decides how to move forward. In this case, > >> > that will also resolve whether or not it can be committed to trunk. > >> > > >> > If this logic is unpersuasive, then we can require a 2/3 majority to > >> > replace the codebase. Either way, the PMC will vote to define the > >> > consensus view when it is not emergent. > >> > > >> > > This issue has good visibility and enough discussion. > >> > > >> > Yes, it has. We always prefer consensus to voting, but when discussion > >> > reveals that complete consensus is impossible, we still need a way > >> > forward. This is rare, and usually reserved for significant changes > >> > (like merging YARN). Frankly, it's embarrassing to resort to it here, > >> > but here we are. > >> > > >> > > If there is a binding veto in effect then the change must be > >> > > abandoned. > >> > Else you should be able to proceed with committing. However, 3.0.0 > must > >> > be > >> > called out as an abandoned release if we commit it. > >> > > >> > This is not accurate. A binding veto from any committer halts > >> > progress, but the PMC sets the direction of the project. That includes > >> > making decisions that are not universally accepted. -C > >> > > >> > > On 2/1/18, 3:01 PM, "Lei Xu" wrote: > >> > > > >> > > Sounds good to me, ATM. > >> > > > >> > > On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers > >> > wrote: > >> > > > Hey Anu, > >> > > > > >> > > > My feeling on HDFS-12990 is that we've discussed it quite a > bit > >> > already and > >> > > > it doesn't seem at this point like either side is going to > >> > > budge. > >> > I'm > >> > > > certainly happy to have a phone call about it, but I don't > >> > > expect > >> > that we'd > >> > > > make much progress. > >> > > > > >> > > > My suggestion is that we simply include the patch posted to > >> > HDFS-12990 in > >> > > > the 3.0.1 RC and call this issue out clearly in the subsequent > >> > VOTE thread > >> > > > for the 3.0.1 release. Eddy, are you up for that? > >> > > > > >> > > > Best, > >> > > > Aaron > >> > > > > >> > > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu > wrote: > >> > > >> > >> > > >> +Xiao > >> > > >> > >> > > >> My understanding is that we will have this for 3.0.1. Xiao, > >> > could > >> > > >> you give your inputs here? > >> > > >> > >> > > >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer < > >> > aengin...@hortonworks.com> > >> > > >> wrote: > >> > > >> > Hi Eddy, > >> > > >> > > >> > > >> > Thanks for driving this release. Just a quick question, do > we > >> > have time > >> > > >> > to close this issue? > >> > > >> > https://issues.apache.org/jira/browse/HDFS-12990 > >> > > >> > > >> > > >> > or are we abandoning it? I believe that this is the last > >> > > window > >> > for us > >> > > >> > to fix this issue. > >> > > >> > > >> > > >> > Should we have a call and get this resolved one way or > >> > > another? > >> > > >> > > >> > > >> > Thanks > >> > > >> > Anu > >> > > >> > > >> > > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > >> > > >> > > >> > > >> > Hi, All > >> > > >> > > >> > > >> > I just cut branch-3.0.1 from branch-3.0. Please make > >> > > sure > >> > all > >> > > >> > patches > >> > > >> > targeted to 3.0.1 being checked in both branch-3.0 and > >> > branch-3.0.1. > >> > > >> > > >> > > >> > Thanks! > >> > > >> > Eddy > >> > > >> > > >> > > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu > >> > > > >> > wrote: > >> > >
Re: Apache Hadoop 3.0.1 Release plan
Hi, Brahma Thanks for reminder. YARN-5742 does not look like a blocker to me. I will create a RC right after HADOOP-14060. On Thu, Feb 8, 2018 at 7:35 AM, Kihwal Leewrote: > HADOOP-14060 is a blocker. Daryn will add more detail to the jira or to > this thread. > > On Thu, Feb 8, 2018 at 7:01 AM, Brahma Reddy Battula > wrote: >> >> Hi Eddy, >> >> HDFS-12990 got committed to 3.0.1,can we have RC for 3.0.1 (only >> YARN-5742 >> blocker is open ) ? >> >> >> On Sat, Feb 3, 2018 at 12:40 AM, Chris Douglas >> wrote: >> >> > On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwal >> > >> > wrote: >> > > Do you plan to roll an RC with an uncommitted fix? That isn't the >> > > right >> > approach. >> > >> > The fix will be committed to the release branch. We'll vote on the >> > release, and if it receives a majority of +1 votes then it becomes >> > 3.0.1. That's how the PMC decides how to move forward. In this case, >> > that will also resolve whether or not it can be committed to trunk. >> > >> > If this logic is unpersuasive, then we can require a 2/3 majority to >> > replace the codebase. Either way, the PMC will vote to define the >> > consensus view when it is not emergent. >> > >> > > This issue has good visibility and enough discussion. >> > >> > Yes, it has. We always prefer consensus to voting, but when discussion >> > reveals that complete consensus is impossible, we still need a way >> > forward. This is rare, and usually reserved for significant changes >> > (like merging YARN). Frankly, it's embarrassing to resort to it here, >> > but here we are. >> > >> > > If there is a binding veto in effect then the change must be >> > > abandoned. >> > Else you should be able to proceed with committing. However, 3.0.0 must >> > be >> > called out as an abandoned release if we commit it. >> > >> > This is not accurate. A binding veto from any committer halts >> > progress, but the PMC sets the direction of the project. That includes >> > making decisions that are not universally accepted. -C >> > >> > > On 2/1/18, 3:01 PM, "Lei Xu" wrote: >> > > >> > > Sounds good to me, ATM. >> > > >> > > On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers >> > wrote: >> > > > Hey Anu, >> > > > >> > > > My feeling on HDFS-12990 is that we've discussed it quite a bit >> > already and >> > > > it doesn't seem at this point like either side is going to >> > > budge. >> > I'm >> > > > certainly happy to have a phone call about it, but I don't >> > > expect >> > that we'd >> > > > make much progress. >> > > > >> > > > My suggestion is that we simply include the patch posted to >> > HDFS-12990 in >> > > > the 3.0.1 RC and call this issue out clearly in the subsequent >> > VOTE thread >> > > > for the 3.0.1 release. Eddy, are you up for that? >> > > > >> > > > Best, >> > > > Aaron >> > > > >> > > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: >> > > >> >> > > >> +Xiao >> > > >> >> > > >> My understanding is that we will have this for 3.0.1. Xiao, >> > could >> > > >> you give your inputs here? >> > > >> >> > > >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer < >> > aengin...@hortonworks.com> >> > > >> wrote: >> > > >> > Hi Eddy, >> > > >> > >> > > >> > Thanks for driving this release. Just a quick question, do we >> > have time >> > > >> > to close this issue? >> > > >> > https://issues.apache.org/jira/browse/HDFS-12990 >> > > >> > >> > > >> > or are we abandoning it? I believe that this is the last >> > > window >> > for us >> > > >> > to fix this issue. >> > > >> > >> > > >> > Should we have a call and get this resolved one way or >> > > another? >> > > >> > >> > > >> > Thanks >> > > >> > Anu >> > > >> > >> > > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: >> > > >> > >> > > >> > Hi, All >> > > >> > >> > > >> > I just cut branch-3.0.1 from branch-3.0. Please make >> > > sure >> > all >> > > >> > patches >> > > >> > targeted to 3.0.1 being checked in both branch-3.0 and >> > branch-3.0.1. >> > > >> > >> > > >> > Thanks! >> > > >> > Eddy >> > > >> > >> > > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu >> > > >> > wrote: >> > > >> > > Hi, All >> > > >> > > >> > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. >> > > To >> > further >> > > >> > > improve the quality of release, we plan to cut >> > branch-3.0.1 branch >> > > >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 >> > release. The >> > > >> > focus >> > > >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) >> > and bug >> > > >> > fixes >> > > >> > > [2]. No new features and
Re: Apache Hadoop 3.0.1 Release plan
HADOOP-14060 is a blocker. Daryn will add more detail to the jira or to this thread. On Thu, Feb 8, 2018 at 7:01 AM, Brahma Reddy Battulawrote: > Hi Eddy, > > HDFS-12990 got committed to 3.0.1,can we have RC for 3.0.1 (only YARN-5742 > blocker is open ) ? > > > On Sat, Feb 3, 2018 at 12:40 AM, Chris Douglas > wrote: > > > On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwal > > > wrote: > > > Do you plan to roll an RC with an uncommitted fix? That isn't the right > > approach. > > > > The fix will be committed to the release branch. We'll vote on the > > release, and if it receives a majority of +1 votes then it becomes > > 3.0.1. That's how the PMC decides how to move forward. In this case, > > that will also resolve whether or not it can be committed to trunk. > > > > If this logic is unpersuasive, then we can require a 2/3 majority to > > replace the codebase. Either way, the PMC will vote to define the > > consensus view when it is not emergent. > > > > > This issue has good visibility and enough discussion. > > > > Yes, it has. We always prefer consensus to voting, but when discussion > > reveals that complete consensus is impossible, we still need a way > > forward. This is rare, and usually reserved for significant changes > > (like merging YARN). Frankly, it's embarrassing to resort to it here, > > but here we are. > > > > > If there is a binding veto in effect then the change must be abandoned. > > Else you should be able to proceed with committing. However, 3.0.0 must > be > > called out as an abandoned release if we commit it. > > > > This is not accurate. A binding veto from any committer halts > > progress, but the PMC sets the direction of the project. That includes > > making decisions that are not universally accepted. -C > > > > > On 2/1/18, 3:01 PM, "Lei Xu" wrote: > > > > > > Sounds good to me, ATM. > > > > > > On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers > > wrote: > > > > Hey Anu, > > > > > > > > My feeling on HDFS-12990 is that we've discussed it quite a bit > > already and > > > > it doesn't seem at this point like either side is going to budge. > > I'm > > > > certainly happy to have a phone call about it, but I don't expect > > that we'd > > > > make much progress. > > > > > > > > My suggestion is that we simply include the patch posted to > > HDFS-12990 in > > > > the 3.0.1 RC and call this issue out clearly in the subsequent > > VOTE thread > > > > for the 3.0.1 release. Eddy, are you up for that? > > > > > > > > Best, > > > > Aaron > > > > > > > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: > > > >> > > > >> +Xiao > > > >> > > > >> My understanding is that we will have this for 3.0.1. Xiao, > > could > > > >> you give your inputs here? > > > >> > > > >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer < > > aengin...@hortonworks.com> > > > >> wrote: > > > >> > Hi Eddy, > > > >> > > > > >> > Thanks for driving this release. Just a quick question, do we > > have time > > > >> > to close this issue? > > > >> > https://issues.apache.org/jira/browse/HDFS-12990 > > > >> > > > > >> > or are we abandoning it? I believe that this is the last > window > > for us > > > >> > to fix this issue. > > > >> > > > > >> > Should we have a call and get this resolved one way or > another? > > > >> > > > > >> > Thanks > > > >> > Anu > > > >> > > > > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > > > >> > > > > >> > Hi, All > > > >> > > > > >> > I just cut branch-3.0.1 from branch-3.0. Please make sure > > all > > > >> > patches > > > >> > targeted to 3.0.1 being checked in both branch-3.0 and > > branch-3.0.1. > > > >> > > > > >> > Thanks! > > > >> > Eddy > > > >> > > > > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu > > > wrote: > > > >> > > Hi, All > > > >> > > > > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. To > > further > > > >> > > improve the quality of release, we plan to cut > > branch-3.0.1 branch > > > >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 > > release. The > > > >> > focus > > > >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) > > and bug > > > >> > fixes > > > >> > > [2]. No new features and improvement should be > included. > > > >> > > > > > >> > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote > > for RC on > > > >> > Feb > > > >> > > 1st, targeting for Feb 9th release. > > > >> > > > > > >> > > Please feel free to share your insights. > > > >> > > > > > >> > > [1] > > > >> >
Re: Apache Hadoop 3.0.1 Release plan
Hi Eddy, HDFS-12990 got committed to 3.0.1,can we have RC for 3.0.1 (only YARN-5742 blocker is open ) ? On Sat, Feb 3, 2018 at 12:40 AM, Chris Douglaswrote: > On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwal > wrote: > > Do you plan to roll an RC with an uncommitted fix? That isn't the right > approach. > > The fix will be committed to the release branch. We'll vote on the > release, and if it receives a majority of +1 votes then it becomes > 3.0.1. That's how the PMC decides how to move forward. In this case, > that will also resolve whether or not it can be committed to trunk. > > If this logic is unpersuasive, then we can require a 2/3 majority to > replace the codebase. Either way, the PMC will vote to define the > consensus view when it is not emergent. > > > This issue has good visibility and enough discussion. > > Yes, it has. We always prefer consensus to voting, but when discussion > reveals that complete consensus is impossible, we still need a way > forward. This is rare, and usually reserved for significant changes > (like merging YARN). Frankly, it's embarrassing to resort to it here, > but here we are. > > > If there is a binding veto in effect then the change must be abandoned. > Else you should be able to proceed with committing. However, 3.0.0 must be > called out as an abandoned release if we commit it. > > This is not accurate. A binding veto from any committer halts > progress, but the PMC sets the direction of the project. That includes > making decisions that are not universally accepted. -C > > > On 2/1/18, 3:01 PM, "Lei Xu" wrote: > > > > Sounds good to me, ATM. > > > > On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers > wrote: > > > Hey Anu, > > > > > > My feeling on HDFS-12990 is that we've discussed it quite a bit > already and > > > it doesn't seem at this point like either side is going to budge. > I'm > > > certainly happy to have a phone call about it, but I don't expect > that we'd > > > make much progress. > > > > > > My suggestion is that we simply include the patch posted to > HDFS-12990 in > > > the 3.0.1 RC and call this issue out clearly in the subsequent > VOTE thread > > > for the 3.0.1 release. Eddy, are you up for that? > > > > > > Best, > > > Aaron > > > > > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: > > >> > > >> +Xiao > > >> > > >> My understanding is that we will have this for 3.0.1. Xiao, > could > > >> you give your inputs here? > > >> > > >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer < > aengin...@hortonworks.com> > > >> wrote: > > >> > Hi Eddy, > > >> > > > >> > Thanks for driving this release. Just a quick question, do we > have time > > >> > to close this issue? > > >> > https://issues.apache.org/jira/browse/HDFS-12990 > > >> > > > >> > or are we abandoning it? I believe that this is the last window > for us > > >> > to fix this issue. > > >> > > > >> > Should we have a call and get this resolved one way or another? > > >> > > > >> > Thanks > > >> > Anu > > >> > > > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > > >> > > > >> > Hi, All > > >> > > > >> > I just cut branch-3.0.1 from branch-3.0. Please make sure > all > > >> > patches > > >> > targeted to 3.0.1 being checked in both branch-3.0 and > branch-3.0.1. > > >> > > > >> > Thanks! > > >> > Eddy > > >> > > > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu > wrote: > > >> > > Hi, All > > >> > > > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. To > further > > >> > > improve the quality of release, we plan to cut > branch-3.0.1 branch > > >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 > release. The > > >> > focus > > >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) > and bug > > >> > fixes > > >> > > [2]. No new features and improvement should be included. > > >> > > > > >> > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote > for RC on > > >> > Feb > > >> > > 1st, targeting for Feb 9th release. > > >> > > > > >> > > Please feel free to share your insights. > > >> > > > > >> > > [1] > > >> > https://www.mail-archive.com/general@hadoop.apache.org/ > msg07757.html > > >> > > [2] https://issues.apache.org/ > jira/issues/?filter=12342842 > > >> > > > > >> > > Best, > > >> > > -- > > >> > > Lei (Eddy) Xu > > >> > > Software Engineer, Cloudera > > >> > > > >> > > > >> > > > >> > -- > > >> > Lei (Eddy) Xu > > >> > Software Engineer, Cloudera > > >> > > > >> > > >
Re: Apache Hadoop 3.0.1 Release plan
On Fri, Feb 2, 2018 at 10:22 AM, Arpit Agarwalwrote: > Do you plan to roll an RC with an uncommitted fix? That isn't the right > approach. The fix will be committed to the release branch. We'll vote on the release, and if it receives a majority of +1 votes then it becomes 3.0.1. That's how the PMC decides how to move forward. In this case, that will also resolve whether or not it can be committed to trunk. If this logic is unpersuasive, then we can require a 2/3 majority to replace the codebase. Either way, the PMC will vote to define the consensus view when it is not emergent. > This issue has good visibility and enough discussion. Yes, it has. We always prefer consensus to voting, but when discussion reveals that complete consensus is impossible, we still need a way forward. This is rare, and usually reserved for significant changes (like merging YARN). Frankly, it's embarrassing to resort to it here, but here we are. > If there is a binding veto in effect then the change must be abandoned. Else > you should be able to proceed with committing. However, 3.0.0 must be called > out as an abandoned release if we commit it. This is not accurate. A binding veto from any committer halts progress, but the PMC sets the direction of the project. That includes making decisions that are not universally accepted. -C > On 2/1/18, 3:01 PM, "Lei Xu" wrote: > > Sounds good to me, ATM. > > On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers wrote: > > Hey Anu, > > > > My feeling on HDFS-12990 is that we've discussed it quite a bit already > and > > it doesn't seem at this point like either side is going to budge. I'm > > certainly happy to have a phone call about it, but I don't expect that > we'd > > make much progress. > > > > My suggestion is that we simply include the patch posted to HDFS-12990 > in > > the 3.0.1 RC and call this issue out clearly in the subsequent VOTE > thread > > for the 3.0.1 release. Eddy, are you up for that? > > > > Best, > > Aaron > > > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: > >> > >> +Xiao > >> > >> My understanding is that we will have this for 3.0.1. Xiao, could > >> you give your inputs here? > >> > >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer > > >> wrote: > >> > Hi Eddy, > >> > > >> > Thanks for driving this release. Just a quick question, do we have > time > >> > to close this issue? > >> > https://issues.apache.org/jira/browse/HDFS-12990 > >> > > >> > or are we abandoning it? I believe that this is the last window for > us > >> > to fix this issue. > >> > > >> > Should we have a call and get this resolved one way or another? > >> > > >> > Thanks > >> > Anu > >> > > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > >> > > >> > Hi, All > >> > > >> > I just cut branch-3.0.1 from branch-3.0. Please make sure all > >> > patches > >> > targeted to 3.0.1 being checked in both branch-3.0 and > branch-3.0.1. > >> > > >> > Thanks! > >> > Eddy > >> > > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu > wrote: > >> > > Hi, All > >> > > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. To > further > >> > > improve the quality of release, we plan to cut branch-3.0.1 > branch > >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 release. > The > >> > focus > >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug > >> > fixes > >> > > [2]. No new features and improvement should be included. > >> > > > >> > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for > RC on > >> > Feb > >> > > 1st, targeting for Feb 9th release. > >> > > > >> > > Please feel free to share your insights. > >> > > > >> > > [1] > >> > https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > >> > > [2] https://issues.apache.org/jira/issues/?filter=12342842 > >> > > > >> > > Best, > >> > > -- > >> > > Lei (Eddy) Xu > >> > > Software Engineer, Cloudera > >> > > >> > > >> > > >> > -- > >> > Lei (Eddy) Xu > >> > Software Engineer, Cloudera > >> > > >> > > >> > - > >> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > >> > For additional commands, e-mail: > common-dev-h...@hadoop.apache.org > >> > > >> > > >> > > >> > >> > >> > >> -- > >> Lei (Eddy) Xu > >> Software Engineer, Cloudera > >> > >>
Re: Apache Hadoop 3.0.1 Release plan
Hi Aaron/Lei, Do you plan to roll an RC with an uncommitted fix? That isn't the right approach. This issue has good visibility and enough discussion. If there is a binding veto in effect then the change must be abandoned. Else you should be able to proceed with committing. However, 3.0.0 must be called out as an abandoned release if we commit it. Regards, Arpit On 2/1/18, 3:01 PM, "Lei Xu"wrote: Sounds good to me, ATM. On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myers wrote: > Hey Anu, > > My feeling on HDFS-12990 is that we've discussed it quite a bit already and > it doesn't seem at this point like either side is going to budge. I'm > certainly happy to have a phone call about it, but I don't expect that we'd > make much progress. > > My suggestion is that we simply include the patch posted to HDFS-12990 in > the 3.0.1 RC and call this issue out clearly in the subsequent VOTE thread > for the 3.0.1 release. Eddy, are you up for that? > > Best, > Aaron > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: >> >> +Xiao >> >> My understanding is that we will have this for 3.0.1. Xiao, could >> you give your inputs here? >> >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer >> wrote: >> > Hi Eddy, >> > >> > Thanks for driving this release. Just a quick question, do we have time >> > to close this issue? >> > https://issues.apache.org/jira/browse/HDFS-12990 >> > >> > or are we abandoning it? I believe that this is the last window for us >> > to fix this issue. >> > >> > Should we have a call and get this resolved one way or another? >> > >> > Thanks >> > Anu >> > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: >> > >> > Hi, All >> > >> > I just cut branch-3.0.1 from branch-3.0. Please make sure all >> > patches >> > targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. >> > >> > Thanks! >> > Eddy >> > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wrote: >> > > Hi, All >> > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. To further >> > > improve the quality of release, we plan to cut branch-3.0.1 branch >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The >> > focus >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug >> > fixes >> > > [2]. No new features and improvement should be included. >> > > >> > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on >> > Feb >> > > 1st, targeting for Feb 9th release. >> > > >> > > Please feel free to share your insights. >> > > >> > > [1] >> > https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html >> > > [2] https://issues.apache.org/jira/issues/?filter=12342842 >> > > >> > > Best, >> > > -- >> > > Lei (Eddy) Xu >> > > Software Engineer, Cloudera >> > >> > >> > >> > -- >> > Lei (Eddy) Xu >> > Software Engineer, Cloudera >> > >> > >> > - >> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org >> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org >> > >> > >> > >> >> >> >> -- >> Lei (Eddy) Xu >> Software Engineer, Cloudera >> >> - >> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org >> > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Sounds good to me, ATM. On Thu, Feb 1, 2018 at 2:34 PM, Aaron T. Myerswrote: > Hey Anu, > > My feeling on HDFS-12990 is that we've discussed it quite a bit already and > it doesn't seem at this point like either side is going to budge. I'm > certainly happy to have a phone call about it, but I don't expect that we'd > make much progress. > > My suggestion is that we simply include the patch posted to HDFS-12990 in > the 3.0.1 RC and call this issue out clearly in the subsequent VOTE thread > for the 3.0.1 release. Eddy, are you up for that? > > Best, > Aaron > > On Thu, Feb 1, 2018 at 1:13 PM, Lei Xu wrote: >> >> +Xiao >> >> My understanding is that we will have this for 3.0.1. Xiao, could >> you give your inputs here? >> >> On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer >> wrote: >> > Hi Eddy, >> > >> > Thanks for driving this release. Just a quick question, do we have time >> > to close this issue? >> > https://issues.apache.org/jira/browse/HDFS-12990 >> > >> > or are we abandoning it? I believe that this is the last window for us >> > to fix this issue. >> > >> > Should we have a call and get this resolved one way or another? >> > >> > Thanks >> > Anu >> > >> > On 2/1/18, 10:51 AM, "Lei Xu" wrote: >> > >> > Hi, All >> > >> > I just cut branch-3.0.1 from branch-3.0. Please make sure all >> > patches >> > targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. >> > >> > Thanks! >> > Eddy >> > >> > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wrote: >> > > Hi, All >> > > >> > > We have released Apache Hadoop 3.0.0 in December [1]. To further >> > > improve the quality of release, we plan to cut branch-3.0.1 branch >> > > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The >> > focus >> > > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug >> > fixes >> > > [2]. No new features and improvement should be included. >> > > >> > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on >> > Feb >> > > 1st, targeting for Feb 9th release. >> > > >> > > Please feel free to share your insights. >> > > >> > > [1] >> > https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html >> > > [2] https://issues.apache.org/jira/issues/?filter=12342842 >> > > >> > > Best, >> > > -- >> > > Lei (Eddy) Xu >> > > Software Engineer, Cloudera >> > >> > >> > >> > -- >> > Lei (Eddy) Xu >> > Software Engineer, Cloudera >> > >> > >> > - >> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org >> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org >> > >> > >> > >> >> >> >> -- >> Lei (Eddy) Xu >> Software Engineer, Cloudera >> >> - >> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org >> > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Hey Anu, My feeling on HDFS-12990 is that we've discussed it quite a bit already and it doesn't seem at this point like either side is going to budge. I'm certainly happy to have a phone call about it, but I don't expect that we'd make much progress. My suggestion is that we simply include the patch posted to HDFS-12990 in the 3.0.1 RC and call this issue out clearly in the subsequent VOTE thread for the 3.0.1 release. Eddy, are you up for that? Best, Aaron On Thu, Feb 1, 2018 at 1:13 PM, Lei Xuwrote: > +Xiao > > My understanding is that we will have this for 3.0.1. Xiao, could > you give your inputs here? > > On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineer > wrote: > > Hi Eddy, > > > > Thanks for driving this release. Just a quick question, do we have time > to close this issue? > > https://issues.apache.org/jira/browse/HDFS-12990 > > > > or are we abandoning it? I believe that this is the last window for us > to fix this issue. > > > > Should we have a call and get this resolved one way or another? > > > > Thanks > > Anu > > > > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > > > > Hi, All > > > > I just cut branch-3.0.1 from branch-3.0. Please make sure all > patches > > targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. > > > > Thanks! > > Eddy > > > > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wrote: > > > Hi, All > > > > > > We have released Apache Hadoop 3.0.0 in December [1]. To further > > > improve the quality of release, we plan to cut branch-3.0.1 branch > > > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The > focus > > > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug > fixes > > > [2]. No new features and improvement should be included. > > > > > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on > Feb > > > 1st, targeting for Feb 9th release. > > > > > > Please feel free to share your insights. > > > > > > [1] https://www.mail-archive.com/general@hadoop.apache.org/ > msg07757.html > > > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > > > > > Best, > > > -- > > > Lei (Eddy) Xu > > > Software Engineer, Cloudera > > > > > > > > -- > > Lei (Eddy) Xu > > Software Engineer, Cloudera > > > > > - > > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > > > > > > > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > - > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > >
Re: Apache Hadoop 3.0.1 Release plan
+Xiao My understanding is that we will have this for 3.0.1. Xiao, could you give your inputs here? On Thu, Feb 1, 2018 at 11:55 AM, Anu Engineerwrote: > Hi Eddy, > > Thanks for driving this release. Just a quick question, do we have time to > close this issue? > https://issues.apache.org/jira/browse/HDFS-12990 > > or are we abandoning it? I believe that this is the last window for us to fix > this issue. > > Should we have a call and get this resolved one way or another? > > Thanks > Anu > > On 2/1/18, 10:51 AM, "Lei Xu" wrote: > > Hi, All > > I just cut branch-3.0.1 from branch-3.0. Please make sure all patches > targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. > > Thanks! > Eddy > > On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wrote: > > Hi, All > > > > We have released Apache Hadoop 3.0.0 in December [1]. To further > > improve the quality of release, we plan to cut branch-3.0.1 branch > > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > > [2]. No new features and improvement should be included. > > > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > > 1st, targeting for Feb 9th release. > > > > Please feel free to share your insights. > > > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > > > Best, > > -- > > Lei (Eddy) Xu > > Software Engineer, Cloudera > > > > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > - > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Hi Eddy, Thanks for driving this release. Just a quick question, do we have time to close this issue? https://issues.apache.org/jira/browse/HDFS-12990 or are we abandoning it? I believe that this is the last window for us to fix this issue. Should we have a call and get this resolved one way or another? Thanks Anu On 2/1/18, 10:51 AM, "Lei Xu"wrote: Hi, All I just cut branch-3.0.1 from branch-3.0. Please make sure all patches targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. Thanks! Eddy On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wrote: > Hi, All > > We have released Apache Hadoop 3.0.0 in December [1]. To further > improve the quality of release, we plan to cut branch-3.0.1 branch > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > [2]. No new features and improvement should be included. > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > 1st, targeting for Feb 9th release. > > Please feel free to share your insights. > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > Best, > -- > Lei (Eddy) Xu > Software Engineer, Cloudera -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Hi, All I just cut branch-3.0.1 from branch-3.0. Please make sure all patches targeted to 3.0.1 being checked in both branch-3.0 and branch-3.0.1. Thanks! Eddy On Tue, Jan 9, 2018 at 11:17 AM, Lei Xuwrote: > Hi, All > > We have released Apache Hadoop 3.0.0 in December [1]. To further > improve the quality of release, we plan to cut branch-3.0.1 branch > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > [2]. No new features and improvement should be included. > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > 1st, targeting for Feb 9th release. > > Please feel free to share your insights. > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > Best, > -- > Lei (Eddy) Xu > Software Engineer, Cloudera -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Hi, Andrew and Jason Thanks for the feedback! I will follow the pattern and cut the branch on Feb 1st and start the RC vote around Feb 5th then. Best On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowewrote: > Is it necessary to cut the branch so far ahead of the release? branch-3.0 > is already a maintenance line for 3.0.x releases. Is there a known > feature/improvement planned to go into branch-3.0 that is not desirable for > the 3.0.1 release? > > I have found in the past that branching so early leads to many useful fixes > being unnecessarily postponed to future releases because committers forget > to pick to the new, relatively long-lived patch branch. This becomes > especially true if blockers end up dragging out the ultimate release date, > which has historically been quite common. My preference would be to cut > this branch as close to the RC as possible. > > Jason > > > On Tue, Jan 9, 2018 at 1:17 PM, Lei Xu wrote: >> >> Hi, All >> >> We have released Apache Hadoop 3.0.0 in December [1]. To further >> improve the quality of release, we plan to cut branch-3.0.1 branch >> tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus >> of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes >> [2]. No new features and improvement should be included. >> >> We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb >> 1st, targeting for Feb 9th release. >> >> Please feel free to share your insights. >> >> [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html >> [2] https://issues.apache.org/jira/issues/?filter=12342842 >> >> Best, >> -- >> Lei (Eddy) Xu >> Software Engineer, Cloudera >> >> - >> To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org >> > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Hi, Andrew and Jason Thanks for the feedback! I will follow the pattern and cut the branch on Feb 1st and start the RC vote around Feb 5th then. Best On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowewrote: > Is it necessary to cut the branch so far ahead of the release? branch-3.0 > is already a maintenance line for 3.0.x releases. Is there a known > feature/improvement planned to go into branch-3.0 that is not desirable for > the 3.0.1 release? > > I have found in the past that branching so early leads to many useful fixes > being unnecessarily postponed to future releases because committers forget > to pick to the new, relatively long-lived patch branch. This becomes > especially true if blockers end up dragging out the ultimate release date, > which has historically been quite common. My preference would be to cut > this branch as close to the RC as possible. > > Jason > > > On Tue, Jan 9, 2018 at 1:17 PM, Lei Xu wrote: >> >> Hi, All >> >> We have released Apache Hadoop 3.0.0 in December [1]. To further >> improve the quality of release, we plan to cut branch-3.0.1 branch >> tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus >> of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes >> [2]. No new features and improvement should be included. >> >> We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb >> 1st, targeting for Feb 9th release. >> >> Please feel free to share your insights. >> >> [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html >> [2] https://issues.apache.org/jira/issues/?filter=12342842 >> >> Best, >> -- >> Lei (Eddy) Xu >> Software Engineer, Cloudera >> >> - >> To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org >> > -- Lei (Eddy) Xu Software Engineer, Cloudera - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
Re: Apache Hadoop 3.0.1 Release plan
Is it necessary to cut the branch so far ahead of the release? branch-3.0 is already a maintenance line for 3.0.x releases. Is there a known feature/improvement planned to go into branch-3.0 that is not desirable for the 3.0.1 release? I have found in the past that branching so early leads to many useful fixes being unnecessarily postponed to future releases because committers forget to pick to the new, relatively long-lived patch branch. This becomes especially true if blockers end up dragging out the ultimate release date, which has historically been quite common. My preference would be to cut this branch as close to the RC as possible. Jason On Tue, Jan 9, 2018 at 1:17 PM, Lei Xuwrote: > Hi, All > > We have released Apache Hadoop 3.0.0 in December [1]. To further > improve the quality of release, we plan to cut branch-3.0.1 branch > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > [2]. No new features and improvement should be included. > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > 1st, targeting for Feb 9th release. > > Please feel free to share your insights. > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > Best, > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > - > To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > >
Re: Apache Hadoop 3.0.1 Release plan
Hi Eddy, thanks for taking this on, Historically we've waited for the first RC to cut the release branch since it keeps things simpler for committers. Also, could you check the permissions on your JIRA filter? It shows as private for me. Best, Andrew On Tue, Jan 9, 2018 at 11:17 AM, Lei Xuwrote: > Hi, All > > We have released Apache Hadoop 3.0.0 in December [1]. To further > improve the quality of release, we plan to cut branch-3.0.1 branch > tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus > of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes > [2]. No new features and improvement should be included. > > We plan to cut branch-3.0.1 tomorrow (Jan 10th) and vote for RC on Feb > 1st, targeting for Feb 9th release. > > Please feel free to share your insights. > > [1] https://www.mail-archive.com/general@hadoop.apache.org/msg07757.html > [2] https://issues.apache.org/jira/issues/?filter=12342842 > > Best, > -- > Lei (Eddy) Xu > Software Engineer, Cloudera > > - > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > >