On Tue, Jul 17, 2018 at 7:21 PM Steve Loughran <ste...@hortonworks.com> wrote:
> > > On 16 Jul 2018, at 23:45, Sunil G <sun...@apache.org<mailto: > sun...@apache.org>> wrote: > > I would also would like to take this opportunity to come up with a detailed > plan. > > - Feature freeze date : all features should be merged by August 10, 2018. > > > > <snip> > > Please let me know if I missed any features targeted to 3.2 per this > > > Well there these big todo lists for S3 & S3Guard. > > https://issues.apache.org/jira/browse/HADOOP-15226 > https://issues.apache.org/jira/browse/HADOOP-15220 > > > There's a bigger bit of work coming on for Azure Datalake Gen 2 > https://issues.apache.org/jira/browse/HADOOP-15407 > > I don't think this is quite ready yet, I've been doing work on it, but if > we have a 3 week deadline, I'm going to expect some timely reviews on > https://issues.apache.org/jira/browse/HADOOP-15546 > > I've uprated that to a blocker feature; will review the S3 & S3Guard JIRAs > to see which of those are blocking. Then there are some pressing "guave, > java 9 prep" > > I can help with this part if you like. > > > > timeline. I would like to volunteer myself as release manager of 3.2.0 > release. > > > well volunteered! > > > Yes, thank you for stepping up. > > I think this raises a good q: what timetable should we have for the 3.2. & > 3.3 releases; if we do want a faster cadence, then having the outline time > from the 3.2 to the 3.3 release means that there's less concern about > things not making the 3.2 dealine > > -Steve > > Good idea to mitigate the short deadline. -AF
