Technically only 20 (at the moment) Jeremy didn't filter out for Bugs only:

https://issues.apache.org/jira/browse/TC-504?jql=project%20%3D%20TC%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20AND%20affectedVersion%20%3D%202.1.0

On Wed, Aug 9, 2017 at 9:14 AM, Jeremy Mitchell <mitchell...@gmail.com>
wrote:

> Here's a link to the major, critical or blocker issues filed against 2.1
> (35 of them as of this writing)
>
> https://issues.apache.org/jira/browse/TC-504?jql=project%20%3D%20TC%20AND%
> 20status%20in%20(Open%2C%20%22In%20Progress%22%2C%
> 20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical%
> 2C%20Major)%20AND%20affectedVersion%20%3D%202.1.0
>
> Doesn't seem like a good idea to ship something with 35 major+ issues filed
> against it. Maybe our Release Manager (Hank) can reach out to the reporter
> of each issue to see if it can be downgraded or fixed prior to RC0? In the
> meantime, like Dave said, let's be proactive and address any issues you've
> reported. I'm looking at mine now.
>
> Jeremy
>
> On Wed, Aug 9, 2017 at 7:53 AM, Dave Neuman <neu...@apache.org> wrote:
>
> > Hey All,
> >
> > I was looking at Jira and noticed that we have 53 unresolved issues
> against
> > TC 2.1 [1].  Of these 53, 6 are Critical or Blocker.  I know that we Hank
> > just cut the 2.1 branch and is thinking about putting out an RC0.  In my
> > opinion we need to address these issues before RC0 is released for
> > testing.  If you have some time can you please take a look at the open
> > issues and help out by either submitting a PR, moving to a different
> > release, or closing the issue if it truly is resolved?
> >
> > Thanks,
> > Dave
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/TC-489?filter=12341560
> >
>

Reply via email to