Hi Jon,

A bug bash would be useful, at least to have issues that can be resolved/
closed figured out. We can then also have follow ons to help drive patches
that are already up. This might be the longer tail but for starters we
should certainly do a scrub.

Regards,
Kuhu Shukla

On Thu, Jul 23, 2020, 00:17 László Bodor <[email protected]> wrote:

> Hi Jonathan!
>
> Could you please share further details about the slack forum? How can I
> join? (It rejects my google acc.)
>
> Regards,
> Laszlo Bodor
>
> On Wed, 22 Jul 2020 at 21:56, Gurleen Dhody
> <[email protected]> wrote:
>
> > Hello,
> >
> > Hi I am unable to join the slack forum. Is there any way you can help me?
> > Also last year there were regular sync up with mcirosoft and alibaba
> team.
> > Are they still going on ?
> >
> > Thank You,
> > Gurleen
> > ________________________________
> > From: Jonathan Eagles <[email protected]>
> > Sent: Wednesday, July 22, 2020 12:15 PM
> > To: [email protected] <[email protected]>
> > Subject: [EXTERNAL] [DISCUSS] Addressing open jiras
> >
> > As of today there are 1060 open TEZ project jiras spanning our 7 year
> > history. This is an unmanageable number from my perspective. Some of
> these
> > represent customer requests. And some have grown stale and are just
> needing
> > closed.
> >
> > I would like to hear ideas of how to reduce these numbers. Perhaps a bug
> > bash, or a way to distribute the load for analysis. But I want to hear
> from
> > you.
> >
> >
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520TEZ%2520AND%2520resolution%2520%253D%2520Unresolved%2520ORDER%2520BY%2520updated%2520DESC%252C%2520priority%2520DESC&amp;data=02%7C01%7CGurleen.Dhody%40microsoft.com%7Caa3f2c12b3c24a68a15908d82e73aad2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637310421619869977&amp;sdata=0e3Ka%2BX5Lt2DWpnO0iElBdPKaWPKY5uqNcxLOFSVNu4%3D&amp;reserved=0
> >
> > More significantly, 84 of these are in the Patch Available status. This
> > represents value to the Tez
> > project that hasn't been realized. It is most important to drive this to
> > zero. Contributions are valued and we should make sure these are top
> > priority. We could set up a goal of reviewing a few per week. Ideas?
> >
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520TEZ%2520AND%2520status%2520%253D%2520%2522Patch%2520Available%2522%2520&amp;data=02%7C01%7CGurleen.Dhody%40microsoft.com%7Caa3f2c12b3c24a68a15908d82e73aad2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637310421619869977&amp;sdata=f%2FZ1DxCIigpOr7aSvgkeQZqD%2FQdqzt4gckPR7weoTns%3D&amp;reserved=0
> >
> > Furthermore,
> >
> > We have setup a Tez slack to ping developers for review some time ago.
> > apache-tez.slack.com
> >
> > We should either retire this or we should use this resource to help
> > coordinate to look for reviewers on jiras.
> >
> > Let me know your thoughts.
> > Jon Eagles
> > Tez PPMC
> >
>

Reply via email to