Planning for Apache Hadoop 2.6.2
Hi all, Now that 2.6.1 is done, it’s time to look forward to 2.6.2. Things to take care of: (#1) Branch: — The first step in this is getting the branch ready. — As I mentioned before [1], the plan is to rebase branch-2.6 based off branch-2.6.1 i.e. start with 2.6.1 + add patches that are already in today’s branch-2.6. This is because, as I noted before, the other way around of applying 150 odd 2.6.1 patches on today’s 2.6 is very cumbersome. — Unless I hear otherwise, we will start this process next week. (#2) Release: — My current idea is to consistently roll out a point release every month, so for 2.6.2, we can target an RC exactly a month from now (2.6.1 release date) (#3) Patches — 2.6.2 will have the few patches that committers already put into branch-2.6. In addition, we should triage and analyze tickets that are already marked [2] against 2.6.2. — Thoughts / inputs welcome on any patches that you want in 2.6.2. Please use “Target Version = 2.6.2” if you want any patch in the release. Thanks, +Vinod [1] Re: [VOTE] Release Apache Hadoop 2.6.1 RC0 http://markmail.org/message/co6m5n6zmdpzsdok [2] 2.6.2 Target tickets: https://issues.apache.org/jira/issues/?filter=12333460
Re: Planning for Apache Hadoop 2.6.2
Thanks Vinod for starting the discussion for 2.6.2! I'd like to volunteer as the release manager for 2.6.2 unless there is an objection. As I've worked with Vinod and Akira for 2.6.1 and triaged a number of issues, I feel I should be in a good position to take care of 2.6.2. Let me know your thoughts. Regards, Sangjin On Thu, Sep 24, 2015 at 10:47 AM, Vinod Kumar Vavilapalli < vino...@apache.org> wrote: > Hi all, > > > Now that 2.6.1 is done, it’s time to look forward to 2.6.2. Things to take > care of: > > > (#1) Branch: > > — The first step in this is getting the branch ready. > > — As I mentioned before [1], the plan is to rebase branch-2.6 based off > branch-2.6.1 i.e. start with 2.6.1 + add patches that are already in > today’s branch-2.6. This is because, as I noted before, the other way > around of applying 150 odd 2.6.1 patches on today’s 2.6 is very cumbersome. > > — Unless I hear otherwise, we will start this process next week. > > > (#2) Release: > > — My current idea is to consistently roll out a point release every > month, so for 2.6.2, we can target an RC exactly a month from now (2.6.1 > release date) > > > (#3) Patches > > — 2.6.2 will have the few patches that committers already put into > branch-2.6. In addition, we should triage and analyze tickets that are > already marked [2] against 2.6.2. > > — Thoughts / inputs welcome on any patches that you want in 2.6.2. > Please use “Target Version = 2.6.2” if you want any patch in the release. > > > Thanks, > > +Vinod > > > [1] Re: [VOTE] Release Apache Hadoop 2.6.1 RC0 > http://markmail.org/message/co6m5n6zmdpzsdok > > [2] 2.6.2 Target tickets: > https://issues.apache.org/jira/issues/?filter=12333460 >
Re: Planning for Apache Hadoop 2.6.2
+1. Please take it over, I’ll standby for any help needed. Thanks +Vinod On Sep 24, 2015, at 11:34 AM, Sangjin Lee mailto:sj...@apache.org>> wrote: I'd like to volunteer as the release manager for 2.6.2 unless there is an objection.
Re: Planning for Apache Hadoop 2.6.2
Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for 2.6.2! +1. If there's anything I can help you with, please tell me. Thanks, Akira On 9/25/15 13:23, Vinayakumar B wrote: Thanks Vinod and Sangjin for making 2.6.1 release possible. Apologies for not getting time to verify and vote for the release. I will also be available to help for 2.6.2 if anything required. Thanks, Vinay On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli wrote: +1. Please take it over, I’ll standby for any help needed. Thanks +Vinod On Sep 24, 2015, at 11:34 AM, Sangjin Lee > wrote: I'd like to volunteer as the release manager for 2.6.2 unless there is an objection.
Re: Planning for Apache Hadoop 2.6.2
Thanks folks. I'll get started on the items Vinod mentioned soon. If you have something you'd like to push for inclusion in 2.6.2, please mark the target version as 2.6.2. I'd like to ask one more thing on top of that. It would be AWESOME if you can check if it can be applied cleanly on top of 2.6.1, and if not, provide an updated patch suitable for 2.6.1. This will help speed up the 2.6.2 release process tremendously. If the person who's recommending the JIRA for 2.6.2 inclusion can do it, that would be great. Help from the original contributor might be helpful as well. Thanks for your cooperation! Regards, Sangjin On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA wrote: > Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for > 2.6.2! > > +1. If there's anything I can help you with, please tell me. > > Thanks, > Akira > > > On 9/25/15 13:23, Vinayakumar B wrote: > >> Thanks Vinod and Sangjin for making 2.6.1 release possible. >> >> Apologies for not getting time to verify and vote for the release. >> >> I will also be available to help for 2.6.2 if anything required. >> >> Thanks, >> Vinay >> >> On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < >> vino...@hortonworks.com >> >>> wrote: >>> >> >> +1. Please take it over, I’ll standby for any help needed. >>> >>> Thanks >>> +Vinod >>> >>> >>> On Sep 24, 2015, at 11:34 AM, Sangjin Lee >> sj...@apache.org>> wrote: >>> >>> I'd like to volunteer as the release manager for 2.6.2 unless there is an >>> objection. >>> >>> >>> >> >
Re: Planning for Apache Hadoop 2.6.2
Per Vinod's suggestion, in order to reduce the amount of movement I'll pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the other way around. This means I'll need to move branch-2.6 and force push that change. Could you please hold off on committing to branch-2.6 until I am done relocating the branch? I'll let you know when I'm done with that exercise. I expect I'll be done with this in 24 hours or so. Let me know if you have any concerns. Thanks, Sangjin On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: > Thanks folks. I'll get started on the items Vinod mentioned soon. > > If you have something you'd like to push for inclusion in 2.6.2, please > mark the target version as 2.6.2. > > I'd like to ask one more thing on top of that. It would be AWESOME if you > can check if it can be applied cleanly on top of 2.6.1, and if not, provide > an updated patch suitable for 2.6.1. This will help speed up the 2.6.2 > release process tremendously. If the person who's recommending the JIRA for > 2.6.2 inclusion can do it, that would be great. Help from the original > contributor might be helpful as well. Thanks for your cooperation! > > Regards, > Sangjin > > On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA > wrote: > >> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for >> 2.6.2! >> >> +1. If there's anything I can help you with, please tell me. >> >> Thanks, >> Akira >> >> >> On 9/25/15 13:23, Vinayakumar B wrote: >> >>> Thanks Vinod and Sangjin for making 2.6.1 release possible. >>> >>> Apologies for not getting time to verify and vote for the release. >>> >>> I will also be available to help for 2.6.2 if anything required. >>> >>> Thanks, >>> Vinay >>> >>> On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < >>> vino...@hortonworks.com >>> wrote: >>> >>> +1. Please take it over, I’ll standby for any help needed. Thanks +Vinod On Sep 24, 2015, at 11:34 AM, Sangjin Lee >>> sj...@apache.org>> wrote: I'd like to volunteer as the release manager for 2.6.2 unless there is an objection. >>> >> >
Re: Planning for Apache Hadoop 2.6.2
I have updated branch-2.6 and force pushed the branch. I checked the branch out from scratch and tested building it. Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check if it applies cleanly before committing to branch-2.6. Thanks, Sangjin On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: > Per Vinod's suggestion, in order to reduce the amount of movement I'll > pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the > other way around. This means I'll need to move branch-2.6 and force push > that change. > > Could you please hold off on committing to branch-2.6 until I am done > relocating the branch? I'll let you know when I'm done with that exercise. > I expect I'll be done with this in 24 hours or so. Let me know if you have > any concerns. > > Thanks, > Sangjin > > On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: > >> Thanks folks. I'll get started on the items Vinod mentioned soon. >> >> If you have something you'd like to push for inclusion in 2.6.2, please >> mark the target version as 2.6.2. >> >> I'd like to ask one more thing on top of that. It would be AWESOME if you >> can check if it can be applied cleanly on top of 2.6.1, and if not, provide >> an updated patch suitable for 2.6.1. This will help speed up the 2.6.2 >> release process tremendously. If the person who's recommending the JIRA for >> 2.6.2 inclusion can do it, that would be great. Help from the original >> contributor might be helpful as well. Thanks for your cooperation! >> >> Regards, >> Sangjin >> >> On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < >> ajisa...@oss.nttdata.co.jp> wrote: >> >>> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for >>> 2.6.2! >>> >>> +1. If there's anything I can help you with, please tell me. >>> >>> Thanks, >>> Akira >>> >>> >>> On 9/25/15 13:23, Vinayakumar B wrote: >>> Thanks Vinod and Sangjin for making 2.6.1 release possible. Apologies for not getting time to verify and vote for the release. I will also be available to help for 2.6.2 if anything required. Thanks, Vinay On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < vino...@hortonworks.com > wrote: > +1. Please take it over, I’ll standby for any help needed. > > Thanks > +Vinod > > > On Sep 24, 2015, at 11:34 AM, Sangjin Lee sj...@apache.org>> wrote: > > I'd like to volunteer as the release manager for 2.6.2 unless there is > an > objection. > > > >>> >> >
Re: Planning for Apache Hadoop 2.6.2
Hi all, We are targeting next week to create the first RC for 2.6.2. Currently there are 14 issues that are committed to branch-2.6. If you have bug fixes that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x and would improve the quality of those releases, please take time to review them and commit them to branch-2.6. Also, if you have JIRAs that are targeted to 2.6.2 and are close to being done, this might be a good time to complete them. Do let me know if you have any questions. Thanks, Sangjin On Sat, Sep 26, 2015 at 9:19 AM, Sangjin Lee wrote: > I have updated branch-2.6 and force pushed the branch. I checked the > branch out from scratch and tested building it. > > Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check > if it applies cleanly before committing to branch-2.6. > > Thanks, > Sangjin > > On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: > >> Per Vinod's suggestion, in order to reduce the amount of movement I'll >> pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the >> other way around. This means I'll need to move branch-2.6 and force push >> that change. >> >> Could you please hold off on committing to branch-2.6 until I am done >> relocating the branch? I'll let you know when I'm done with that exercise. >> I expect I'll be done with this in 24 hours or so. Let me know if you have >> any concerns. >> >> Thanks, >> Sangjin >> >> On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: >> >>> Thanks folks. I'll get started on the items Vinod mentioned soon. >>> >>> If you have something you'd like to push for inclusion in 2.6.2, please >>> mark the target version as 2.6.2. >>> >>> I'd like to ask one more thing on top of that. It would be AWESOME if >>> you can check if it can be applied cleanly on top of 2.6.1, and if not, >>> provide an updated patch suitable for 2.6.1. This will help speed up the >>> 2.6.2 release process tremendously. If the person who's recommending the >>> JIRA for 2.6.2 inclusion can do it, that would be great. Help from the >>> original contributor might be helpful as well. Thanks for your cooperation! >>> >>> Regards, >>> Sangjin >>> >>> On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < >>> ajisa...@oss.nttdata.co.jp> wrote: >>> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for 2.6.2! +1. If there's anything I can help you with, please tell me. Thanks, Akira On 9/25/15 13:23, Vinayakumar B wrote: > Thanks Vinod and Sangjin for making 2.6.1 release possible. > > Apologies for not getting time to verify and vote for the release. > > I will also be available to help for 2.6.2 if anything required. > > Thanks, > Vinay > > On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < > vino...@hortonworks.com > >> wrote: >> > > +1. Please take it over, I’ll standby for any help needed. >> >> Thanks >> +Vinod >> >> >> On Sep 24, 2015, at 11:34 AM, Sangjin Lee > sj...@apache.org>> wrote: >> >> I'd like to volunteer as the release manager for 2.6.2 unless there >> is an >> objection. >> >> >> > >>> >> >
Re: Planning for Apache Hadoop 2.6.2
Another friendly reminder that I'll be cutting the branch and creating the RC soon. I'm targeting tomorrow. Thanks! Sangjin On Mon, Oct 12, 2015 at 11:40 AM, Sangjin Lee wrote: > Hi all, > > We are targeting next week to create the first RC for 2.6.2. Currently > there are 14 issues that are committed to branch-2.6. If you have bug fixes > that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x > and would improve the quality of those releases, please take time to review > them and commit them to branch-2.6. > > Also, if you have JIRAs that are targeted to 2.6.2 and are close to being > done, this might be a good time to complete them. > > Do let me know if you have any questions. > > Thanks, > Sangjin > > On Sat, Sep 26, 2015 at 9:19 AM, Sangjin Lee wrote: > >> I have updated branch-2.6 and force pushed the branch. I checked the >> branch out from scratch and tested building it. >> >> Branch-2.6 is back open. If you have a patch ready for 2.6.2, double >> check if it applies cleanly before committing to branch-2.6. >> >> Thanks, >> Sangjin >> >> On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: >> >>> Per Vinod's suggestion, in order to reduce the amount of movement I'll >>> pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the >>> other way around. This means I'll need to move branch-2.6 and force push >>> that change. >>> >>> Could you please hold off on committing to branch-2.6 until I am done >>> relocating the branch? I'll let you know when I'm done with that exercise. >>> I expect I'll be done with this in 24 hours or so. Let me know if you have >>> any concerns. >>> >>> Thanks, >>> Sangjin >>> >>> On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: >>> Thanks folks. I'll get started on the items Vinod mentioned soon. If you have something you'd like to push for inclusion in 2.6.2, please mark the target version as 2.6.2. I'd like to ask one more thing on top of that. It would be AWESOME if you can check if it can be applied cleanly on top of 2.6.1, and if not, provide an updated patch suitable for 2.6.1. This will help speed up the 2.6.2 release process tremendously. If the person who's recommending the JIRA for 2.6.2 inclusion can do it, that would be great. Help from the original contributor might be helpful as well. Thanks for your cooperation! Regards, Sangjin On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < ajisa...@oss.nttdata.co.jp> wrote: > Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion > for 2.6.2! > > +1. If there's anything I can help you with, please tell me. > > Thanks, > Akira > > > On 9/25/15 13:23, Vinayakumar B wrote: > >> Thanks Vinod and Sangjin for making 2.6.1 release possible. >> >> Apologies for not getting time to verify and vote for the release. >> >> I will also be available to help for 2.6.2 if anything required. >> >> Thanks, >> Vinay >> >> On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < >> vino...@hortonworks.com >> >>> wrote: >>> >> >> +1. Please take it over, I’ll standby for any help needed. >>> >>> Thanks >>> +Vinod >>> >>> >>> On Sep 24, 2015, at 11:34 AM, Sangjin Lee >> sj...@apache.org>> wrote: >>> >>> I'd like to volunteer as the release manager for 2.6.2 unless there >>> is an >>> objection. >>> >>> >>> >> > >>> >> >
Re: Planning for Apache Hadoop 2.6.2
If you have backported bugfixes to 2.7.2, please take a moment to consider if it is relevant (and important) for 2.6.x too, and if so backport it to branch-2.6. Thanks! On Tue, Oct 20, 2015 at 9:33 AM, Sangjin Lee wrote: > Another friendly reminder that I'll be cutting the branch and creating the > RC soon. I'm targeting tomorrow. Thanks! > > Sangjin > > On Mon, Oct 12, 2015 at 11:40 AM, Sangjin Lee wrote: > >> Hi all, >> >> We are targeting next week to create the first RC for 2.6.2. Currently >> there are 14 issues that are committed to branch-2.6. If you have bug fixes >> that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x >> and would improve the quality of those releases, please take time to review >> them and commit them to branch-2.6. >> >> Also, if you have JIRAs that are targeted to 2.6.2 and are close to being >> done, this might be a good time to complete them. >> >> Do let me know if you have any questions. >> >> Thanks, >> Sangjin >> >> On Sat, Sep 26, 2015 at 9:19 AM, Sangjin Lee wrote: >> >>> I have updated branch-2.6 and force pushed the branch. I checked the >>> branch out from scratch and tested building it. >>> >>> Branch-2.6 is back open. If you have a patch ready for 2.6.2, double >>> check if it applies cleanly before committing to branch-2.6. >>> >>> Thanks, >>> Sangjin >>> >>> On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: >>> Per Vinod's suggestion, in order to reduce the amount of movement I'll pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the other way around. This means I'll need to move branch-2.6 and force push that change. Could you please hold off on committing to branch-2.6 until I am done relocating the branch? I'll let you know when I'm done with that exercise. I expect I'll be done with this in 24 hours or so. Let me know if you have any concerns. Thanks, Sangjin On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: > Thanks folks. I'll get started on the items Vinod mentioned soon. > > If you have something you'd like to push for inclusion in 2.6.2, > please mark the target version as 2.6.2. > > I'd like to ask one more thing on top of that. It would be AWESOME if > you can check if it can be applied cleanly on top of 2.6.1, and if not, > provide an updated patch suitable for 2.6.1. This will help speed up the > 2.6.2 release process tremendously. If the person who's recommending the > JIRA for 2.6.2 inclusion can do it, that would be great. Help from the > original contributor might be helpful as well. Thanks for your > cooperation! > > Regards, > Sangjin > > On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < > ajisa...@oss.nttdata.co.jp> wrote: > >> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion >> for 2.6.2! >> >> +1. If there's anything I can help you with, please tell me. >> >> Thanks, >> Akira >> >> >> On 9/25/15 13:23, Vinayakumar B wrote: >> >>> Thanks Vinod and Sangjin for making 2.6.1 release possible. >>> >>> Apologies for not getting time to verify and vote for the release. >>> >>> I will also be available to help for 2.6.2 if anything required. >>> >>> Thanks, >>> Vinay >>> >>> On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < >>> vino...@hortonworks.com >>> wrote: >>> >>> +1. Please take it over, I’ll standby for any help needed. Thanks +Vinod On Sep 24, 2015, at 11:34 AM, Sangjin Lee >>> sj...@apache.org>> wrote: I'd like to volunteer as the release manager for 2.6.2 unless there is an objection. >>> >> > >>> >> >
Re: Planning for Apache Hadoop 2.6.2
Thanks for your notification, Sangjin. I'll backport YARN-3798 soon. - Tsuyoshi On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote: > If you have backported bugfixes to 2.7.2, please take a moment to consider > if it is relevant (and important) for 2.6.x too, and if so backport it to > branch-2.6. Thanks! > > On Tue, Oct 20, 2015 at 9:33 AM, Sangjin Lee wrote: > >> Another friendly reminder that I'll be cutting the branch and creating the >> RC soon. I'm targeting tomorrow. Thanks! >> >> Sangjin >> >> On Mon, Oct 12, 2015 at 11:40 AM, Sangjin Lee wrote: >> >>> Hi all, >>> >>> We are targeting next week to create the first RC for 2.6.2. Currently >>> there are 14 issues that are committed to branch-2.6. If you have bug fixes >>> that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x >>> and would improve the quality of those releases, please take time to review >>> them and commit them to branch-2.6. >>> >>> Also, if you have JIRAs that are targeted to 2.6.2 and are close to being >>> done, this might be a good time to complete them. >>> >>> Do let me know if you have any questions. >>> >>> Thanks, >>> Sangjin >>> >>> On Sat, Sep 26, 2015 at 9:19 AM, Sangjin Lee wrote: >>> I have updated branch-2.6 and force pushed the branch. I checked the branch out from scratch and tested building it. Branch-2.6 is back open. If you have a patch ready for 2.6.2, double check if it applies cleanly before committing to branch-2.6. Thanks, Sangjin On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: > Per Vinod's suggestion, in order to reduce the amount of movement I'll > pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the > other way around. This means I'll need to move branch-2.6 and force push > that change. > > Could you please hold off on committing to branch-2.6 until I am done > relocating the branch? I'll let you know when I'm done with that exercise. > I expect I'll be done with this in 24 hours or so. Let me know if you have > any concerns. > > Thanks, > Sangjin > > On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: > >> Thanks folks. I'll get started on the items Vinod mentioned soon. >> >> If you have something you'd like to push for inclusion in 2.6.2, >> please mark the target version as 2.6.2. >> >> I'd like to ask one more thing on top of that. It would be AWESOME if >> you can check if it can be applied cleanly on top of 2.6.1, and if not, >> provide an updated patch suitable for 2.6.1. This will help speed up the >> 2.6.2 release process tremendously. If the person who's recommending the >> JIRA for 2.6.2 inclusion can do it, that would be great. Help from the >> original contributor might be helpful as well. Thanks for your >> cooperation! >> >> Regards, >> Sangjin >> >> On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < >> ajisa...@oss.nttdata.co.jp> wrote: >> >>> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion >>> for 2.6.2! >>> >>> +1. If there's anything I can help you with, please tell me. >>> >>> Thanks, >>> Akira >>> >>> >>> On 9/25/15 13:23, Vinayakumar B wrote: >>> Thanks Vinod and Sangjin for making 2.6.1 release possible. Apologies for not getting time to verify and vote for the release. I will also be available to help for 2.6.2 if anything required. Thanks, Vinay On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < vino...@hortonworks.com > wrote: > +1. Please take it over, I’ll standby for any help needed. > > Thanks > +Vinod > > > On Sep 24, 2015, at 11:34 AM, Sangjin Lee sj...@apache.org>> wrote: > > I'd like to volunteer as the release manager for 2.6.2 unless there > is an > objection. > > > >>> >> > >>> >>
Re: Planning for Apache Hadoop 2.6.2
Done. - Tsuyoshi On Wed, Oct 21, 2015 at 8:53 PM, Tsuyoshi Ozawa wrote: > Thanks for your notification, Sangjin. I'll backport YARN-3798 soon. > > - Tsuyoshi > > On Wed, Oct 21, 2015 at 10:09 AM, Sangjin Lee wrote: >> If you have backported bugfixes to 2.7.2, please take a moment to consider >> if it is relevant (and important) for 2.6.x too, and if so backport it to >> branch-2.6. Thanks! >> >> On Tue, Oct 20, 2015 at 9:33 AM, Sangjin Lee wrote: >> >>> Another friendly reminder that I'll be cutting the branch and creating the >>> RC soon. I'm targeting tomorrow. Thanks! >>> >>> Sangjin >>> >>> On Mon, Oct 12, 2015 at 11:40 AM, Sangjin Lee wrote: >>> Hi all, We are targeting next week to create the first RC for 2.6.2. Currently there are 14 issues that are committed to branch-2.6. If you have bug fixes that were made to branch-2 and/or branch-2.7 that are applicable to 2.6.x and would improve the quality of those releases, please take time to review them and commit them to branch-2.6. Also, if you have JIRAs that are targeted to 2.6.2 and are close to being done, this might be a good time to complete them. Do let me know if you have any questions. Thanks, Sangjin On Sat, Sep 26, 2015 at 9:19 AM, Sangjin Lee wrote: > I have updated branch-2.6 and force pushed the branch. I checked the > branch out from scratch and tested building it. > > Branch-2.6 is back open. If you have a patch ready for 2.6.2, double > check if it applies cleanly before committing to branch-2.6. > > Thanks, > Sangjin > > On Fri, Sep 25, 2015 at 4:42 PM, Sangjin Lee wrote: > >> Per Vinod's suggestion, in order to reduce the amount of movement I'll >> pick commits from branch-2.6 onto the tip of branch-2.6.1 rather than the >> other way around. This means I'll need to move branch-2.6 and force push >> that change. >> >> Could you please hold off on committing to branch-2.6 until I am done >> relocating the branch? I'll let you know when I'm done with that >> exercise. >> I expect I'll be done with this in 24 hours or so. Let me know if you >> have >> any concerns. >> >> Thanks, >> Sangjin >> >> On Fri, Sep 25, 2015 at 12:53 PM, Sangjin Lee wrote: >> >>> Thanks folks. I'll get started on the items Vinod mentioned soon. >>> >>> If you have something you'd like to push for inclusion in 2.6.2, >>> please mark the target version as 2.6.2. >>> >>> I'd like to ask one more thing on top of that. It would be AWESOME if >>> you can check if it can be applied cleanly on top of 2.6.1, and if not, >>> provide an updated patch suitable for 2.6.1. This will help speed up the >>> 2.6.2 release process tremendously. If the person who's recommending the >>> JIRA for 2.6.2 inclusion can do it, that would be great. Help from the >>> original contributor might be helpful as well. Thanks for your >>> cooperation! >>> >>> Regards, >>> Sangjin >>> >>> On Thu, Sep 24, 2015 at 9:39 PM, Akira AJISAKA < >>> ajisa...@oss.nttdata.co.jp> wrote: >>> Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for 2.6.2! +1. If there's anything I can help you with, please tell me. Thanks, Akira On 9/25/15 13:23, Vinayakumar B wrote: > Thanks Vinod and Sangjin for making 2.6.1 release possible. > > Apologies for not getting time to verify and vote for the release. > > I will also be available to help for 2.6.2 if anything required. > > Thanks, > Vinay > > On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli < > vino...@hortonworks.com > >> wrote: >> > > +1. Please take it over, I’ll standby for any help needed. >> >> Thanks >> +Vinod >> >> >> On Sep 24, 2015, at 11:34 AM, Sangjin Lee > sj...@apache.org>> wrote: >> >> I'd like to volunteer as the release manager for 2.6.2 unless there >> is an >> objection. >> >> >> > >>> >> > >>>