This is the status for now: 5 closed/resolved 4 in progress. Rest are in open status.
Total were a total of about 28 or 29 when I sent the email. Guess 10 more tickets were added to label for bug bash later. So, above status is for 40 tickets. On Tue, May 19, 2020 at 11:55 PM Vinoth Chandar <[email protected]> wrote: > Hi siva, > > Can we do a quick update on progress so far? So everyone gets a sense of > how this is going :) > > > > On Fri, May 15, 2020 at 5:19 PM Sivabalan <[email protected]> wrote: > > > Sure Ethan. Will keep you posted if something comes up. > > > > > > On Fri, May 15, 2020 at 1:09 PM Y Ethan Guo <[email protected]> > > wrote: > > > > > Thanks for putting this together, Siva and folks! > > > > > > I'm currently blocked on my other PR, so if there are bug bash tickets > > > unassigned or not worked on, I can pick up one at this time. > > > > > > On Fri, May 15, 2020 at 6:31 AM Sivabalan <[email protected]> wrote: > > > > > > > As we discussed earlier in our mailing list, here we are commencing > our > > > bug > > > > bash for 0.6.0. This is a tracking ticket > > > > <https://issues.apache.org/jira/browse/HUDI-901> for the same. > > > > > > > > Thanks to all who have volunteered to participate. We are looking to > > time > > > > it for 10 days. Planning to wrap it up by 27th of May. Announcing it > > > today > > > > so that folks, will have two full weekends to work on it. > > > > > > > > We have done our best to assign tickets to those who might have good > > > > context and to those who volunteered for bug bash. The cursory > > assignment > > > > is just to help you out, and by no means forcing you to work on it. > If > > > you > > > > feel you can't work on it, feel free to swap with someone here, or > > please > > > > unassign yourself. > > > > > > > > All tickets are labelled with "bug-bash-0.6.0" > > > > < > > > > > > > > > > https://issues.apache.org/jira/browse/HUDI-867?jql=project%20%3D%20HUDI%20AND%20labels%20%3D%20bug-bash-0.6.0 > > > > >. > > > > If anyone feels to pitch in with any of the work you have or > currently > > > > doing, feel free to add the label to your jira ticket, but don't > remove > > > > from existing ones. > > > > > > > > Some tickets are support ones, which might need follow up > > > > questions/clarifications with the reporter of the ticket. For those > try > > > to > > > > start working right away so we can drive to completion by end of day > > 10. > > > > > > > > Once you have the PR up and couldn't find a reviewer or if your PR is > > not > > > > getting reviewed, please reach out to us(vinoth, balaji, leesf, > > vinoyang, > > > > sudha), and they should able to help you out. Or leave a comment in > > your > > > > jira, we will be watching it. > > > > > > > > Again, we totally understand that some tickets may not be completed > by > > > the > > > > time due to various reasons, like support questions, not able to > repro > > > > locally, env mis-match, swamped with some PR work, or don't have > cycles > > > > during these 10 days, etc. Let's try our best to take these to > > > completion, > > > > if you can't get it to completion, it is understandable. But try to > > give > > > it > > > > an attempt. > > > > > > > > We are all ears for any questions or clarification. Please respond > here > > > in > > > > email or you could comment on the jira ticket. Or you could join our > > > > Tuesday sync up meeting for any questions. > > > > > > > > Thanks once again for your contributions in growing the community. > > > > Appreciate it. > > > > > > > > -- > > > > Regards, > > > > - Bug Bash Organizing team > > > > > > > > > > > > > -- > > Regards, > > -Sivabalan > > > -- Regards, -Sivabalan
