Thanks Akira. I'd like to make one small correction. If we're getting HDFS-7704, then we should also get HDFS-7916. My earlier comment was assuming HDFS-7704 was not included in the list. But if is (and I think it should), then we should also get HDFS-7916 as it addresses an important issue related to HDFS-7704. Hope it makes it clear.
Sangjin On Fri, Jul 31, 2015 at 10:01 AM, Akira AJISAKA <ajisa...@oss.nttdata.co.jp> wrote: > Thanks Joep and your team members for creating the list. I really > appreciate your work. I looked your 'not yet marked with 2.6.1-candidate' > list and categorized them. > > 1) Now marked as 2.6.1-candidate and I agree with you to keep it marked. > > * HDFS-7213 > * HDFS-7788 > * HDFS-7884 > * HDFS-7930 > * YARN-2856 > * YARN-3222 > * YARN-3238 > * YARN-3464 > * YARN-3526 > * YARN-3850 > > Thanks Sangjin for creating patches for branch-2.6. > > 2) Not yet marked as 2.6.1-candidate that I'd like to see in 2.6.1 > > * HDFS-7182 > * HDFS-7314 > * HDFS-7704 > * HDFS-7894 > * HDFS-7929 and HDFS-8480 (they are related) > * HDFS-7980 > * HDFS-8245 > * HDFS-8270 > * HDFS-8404 > * HDFS-8486 > * MAPREDUCE-5465 > * MAPREDUCE-5649 > * MAPREDUCE-6166 > * MAPREDUCE-6238 > * MAPREDUCE-6300 > * YARN-2952 > * YARN-2997 > * YARN-3094 > * YARN-3176 (to be fixed soon, I think) > * YARN-3231 > * HADOOP-11295 > * HADOOP-11812 > > 3) Not yet marked as 2.6.1-candidate. I'd like to drop > > * HDFS-7281 (incompatible change) > * HDFS-7446 (this looks to be an improvement) > * HDFS-7916 (cannot apply to branch-2.6 as Sangjin mentioned) > > Hi Vinod, could you mark the issues in 2) as 2.6.1-candidate? > > I'd like to freeze the candidate list in about 7 days and start > backporting them. Do you have any thoughts? > > Regards, > Akira > > > On 7/25/15 10:32, Sangjin Lee wrote: > >> Out of the JIRAs we proposed, please remove HDFS-7916. I don't think it >> applies to 2.6. >> >> Thanks, >> Sangjin >> >> On Wed, Jul 22, 2015 at 4:02 PM, Vinod Kumar Vavilapalli < >> vino...@hortonworks.com> wrote: >> >> I’ve added them all to the 2.6.1-candidate list. I included everything >>> even though some of them are major tickets. The list is getting large, we >>> will have to cut these down once we get down to the next phase of >>> figuring >>> out what to include and what not to. >>> >>> Thanks >>> +Vinod >>> >>> On Jul 21, 2015, at 2:15 AM, Akira AJISAKA <ajisa...@oss.nttdata.co.jp> >>>> >>> wrote: >>> >>>> >>>> Thanks Vinod for updating the candidate list. >>>> I'd like to include the followings 12 JIRAs: >>>> >>>> * YARN-3641 >>>> * YARN-3585 >>>> * YARN-2910 >>>> * HDFS-8431 >>>> * HDFS-7830 >>>> * HDFS-7763 >>>> * HDFS-7742 >>>> * HDFS-7235 >>>> * HDFS-7225 >>>> * MAPREDUCE-6324 >>>> * HADOOP-11934 >>>> * HADOOP-11491 >>>> >>>> Thanks, >>>> Akira >>>> >>>> On 7/18/15 11:13, Vinod Kumar Vavilapalli wrote: >>>> >>>>> - I also have a bunch of patches that I’d like to include, will >>>>> update >>>>> >>>> them right away. >>> >>>> >>>>> I’ve just finished this. The latest 2.6.1-candidate list is up at 64 >>>>> >>>> JIRAs. >>> >>>> >>>>> Others, please look at the list and post anything else you’d like to >>>>> >>>> get included for 2.6.1. >>> >>>> >>>>> Thanks >>>>> +Vinod >>>>> >>>>> >>>>> On Jul 15, 2015, at 6:24 PM, Vinod Kumar Vavilapalli < >>>>> >>>> vino...@hortonworks.com<mailto:vino...@hortonworks.com>> wrote: >>> >>>> >>>>> Alright, I’d like to make progress while the issue is hot. >>>>> >>>>> I created a label to discuss on the candidate list of patches: >>>>> >>>> >>> https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.6.1-candidate >>> < >>> https://issues.apache.org/jira/issues/?jql=labels%20=%202.6.1-candidate> >>> >>>> >>>>> Next steps, I’ll do the following >>>>> - Review 2.7 and 2.8 blocker/critical tickets and see what makes >>>>> sense >>>>> >>>> for 2.6.1 and add as candidates >>> >>>> - I haven’t reviewed the current list yet, the seed list is from this >>>>> >>>> email thread. Will review them. >>> >>>> - I also have a bunch of patches that I’d like to include, will update >>>>> >>>> them right away. >>> >>>> >>>>> Others, please look at the current list and let me know what else you’d >>>>> >>>> like to include. >>> >>>> >>>>> I’d like to keep this ‘candidate-collection’ cycle’ for a max of a week >>>>> >>>> and then start the release process. @Akira, let’s sync up offline on >>> how to >>> take this forward in terms of the release process. >>> >>>> >>>>> Thanks >>>>> +Vinod >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >
