Thanks for all of the JIRA triage for Impala 3.4 so far. I took another pass closing / deferring JIRAs. Here is an updated JIRA query:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20and%20%22Target%20Version%22%20not%20in%20(%22Impala%204.0%22%2C%20%22Product%20Backlog%22) Of these, I current count the following as blockers for Impala 3.4 until determined otherwise: https://issues.apache.org/jira/browse/IMPALA-9357 https://issues.apache.org/jira/browse/IMPALA-9351 https://issues.apache.org/jira/browse/IMPALA-8533 Thanks, Joe On Wed, Feb 12, 2020 at 3:26 PM Tim Armstrong <tarmstr...@cloudera.com> wrote: > I also skimmed the blocker and critical JIRAs. > > I wonder if we need to recalibrate what "blocker" and "critical" mean. In > the past both have been used in Impala with the following meanings: > * Blocker -> we will not do the targeted release until this task is > completed > * Critical -> we will try really hard to finish this task in time for a > release, and maybe we'll delay the release a bit, but we won't necessarily > block the release if it doesn't make it. > > It should be rare to have features or improvements that are blockers or > critical. No matter how awesome or useful they are, or even if it's your > personal #1 priority. > > I think we've gotten some priority inflation and it makes it hard for a > release manager to determine how much needs to be done before the release. > > - Tim > > On Tue, Feb 11, 2020 at 12:00 PM Joe McDonnell <joemcdonn...@cloudera.com> > wrote: > > > I'm going through blocker JIRAs, resolving some and downgrading others. > > Here is an updated link that excludes JIRAs with target version of Impala > > 4.0: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20%3D%20Blocker%20AND%20%22Target%20Version%22%20not%20in%20(%22Impala%204.0%22) > > > > We need to decide if there are features that are close to finished that > > would be nice to get into Impala 3.4. One that I think would be nice to > > merge is Python 3 support for impala-shell (IMPALA-3343). > > > > Thanks, > > Joe > > > > On Mon, Feb 10, 2020 at 7:58 AM Sahil Takiar <takiar.sa...@gmail.com> > > wrote: > > > > > Makes sense to me. > > > > > > On Fri, Feb 7, 2020 at 4:36 PM Aman Sinha <amansi...@gmail.com> wrote: > > > > > > > Thanks Joe for volunteering to be the release manager. > > > > +1 for doing a 3.4 release and for triaging the 'blocker' JIRAs (some > > of > > > > which may turn out not to be real blockers). > > > > > > > > Aman > > > > > > > > On Fri, Feb 7, 2020 at 3:51 PM Tim Armstrong < > tarmstr...@cloudera.com> > > > > wrote: > > > > > > > > > We definitely need to prune down that list of blockers. I suspect > > some > > > of > > > > > them have been fixed since but we should identify the real > > > show-stoppers. > > > > > > > > > > On Fri, Feb 7, 2020 at 1:34 PM Joe McDonnell < > > > joemcdonn...@cloudera.com> > > > > > wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > Impala-3.3.0 was released in August 2019. There have been a lot > of > > > good > > > > > > contributions since then, so I think it would be a good time to > > plan > > > a > > > > > > 3.4.0 release. As discussed on the "Impala 4.x (and 3.x)" thread, > > > after > > > > > the > > > > > > 3.4.0 release, master will become Impala 4. > > > > > > > > > > > > I propose that we release 3.4.0 soon, and I volunteer to be the > > > release > > > > > > manager. I'm interested to hear what the community thinks about > > > doing a > > > > > > release. All feedback is welcome! > > > > > > > > > > > > PS This is not a VOTE thread but only a DISCUSS thread. > > > > > > > > > > > > Thanks, > > > > > > Joe > > > > > > > > > > > > Here is a list of open blocker JIRAs: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20%3D%20Blocker > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Sahil Takiar > > > Software Engineer > > > takiar.sa...@gmail.com | (510) 673-0309 > > > > > >
