Hi Vinod, We've gone through the various lists of upstream jiras and wanted to provide our take on what we'd like to see in 2.6.1 release. In addition, we have ~58 jiras (some a group of work such as DN maintenance state) that we already have in production in a pre-2.6 release. I've gone through and selected those that seem relevant for 2.6.1.
Jiras already marked with 2.6.1-candidate (we agree should be part of 2.6.1): HADOOP-11802 HDFS-7489 HDFS-7533 HDFS-7587 HDFS-7596 HDFS-7707 HDFS-7742 HDFS-8046 HDFS-8072 HDFS-8127 MAPREDUCE-6303 MAPREDUCE-6361 YARN-2414 YARN-2905 YARN-3369 YARN-3485 YARN-3585 YARN-3641 HDFS-7443 HDFS-7575 Jiras not yet marked with 2.6.1-candidate that we'd like to see in 2.6.1: HDFS-7213 HDFS-7446 HDFS-7704 HDFS-7788 HDFS-7884 HDFS-7894 HDFS-7916 HDFS-7929 HDFS-7930 HDFS-7980 HDFS-8245 HDFS-8270 HDFS-8404 HDFS-8480 HDFS-8486 MAPREDUCE-6238 YARN-2856 MAPREDUCE-6300 YARN-2952 YARN-2997 YARN-3094 YARN-3222 YARN-3238 YARN-3464 YARN-3526 YARN-3850 Jiras that we're already running in production pre-2.6 that we'd like in 2.6.1-candidate: HADOOP-11812 (committed in 2.8) MAPREDUCE-5649 (committed in 2.8) YARN-3231 (committed in 2.7) MAPREDUCE-6166 (committed in 2.7) HADOOP-11295 (committed in 2.7) HDFS-7314 (committed in 2.8) HDFS-7182 (committed in 2.7) MAPREDUCE-5465 (committed in 2.8) Lower priority jira that we're already running in production in pre-2.6 that are more a nice to have: HDFS-7281 (committed in 3.0) YARN-3176 (not yet committed in OSS) Note that these lists are a culmination of lots of work by many people in our team, so credit goes to all of them. Any possible typo or mistake in copying jira ids are entirely to be blamed on me. Thanks, Joep On Tue, 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 >> >> >> >
