+1. Good idea.

Thanks,
Haiting


On Thu, Aug 11, 2022 at 10:44 PM Max Xu <maxs...@gmail.com> wrote:

> +1 It would be awesome to utilize the GitHub Project to track issues.
>
> BTW, seems this is a Classic Project[2], and the New Project[1] can provide
> more features than the Classic Project[2].
>
> [1] https://github.com/apache/pulsar/projects?type=new
> [2] https://github.com/apache/pulsar/projects?type=classic
>
>
> Best,
> Max Xu
>
>
> On Thu, Aug 11, 2022 at 11:26 AM Zixuan Liu <node...@gmail.com> wrote:
>
> > +1
> >
> > Thanks,
> > Zixuan
> >
> > Anon Hxy <anonhx...@gmail.com> 于2022年8月11日周四 10:26写道:
> >
> > > +1
> > > Good idea. We are on the way making CI more robust
> > >
> > > Thanks,
> > > Xiaoyu Hou
> > >
> > > PengHui Li <peng...@apache.org> 于2022年8月10日周三 16:35写道:
> > >
> > > > Hi all,
> > > >
> > > > For better tracking flaky test fix, I have tried to create a Github
> > > > Project under the Pulsar repo
> > > https://github.com/apache/pulsar/projects/11
> > > > (It can be removed if we don't like this way)
> > > > This will help us to have a more intuitive view of all the flaky
> tests,
> > > > how many are in progress, in the review stage, and approved.
> > > >
> > > > The project is public for all the contributors, so if you want
> > > > to contribute some flaky tests fixes,
> > > > you can go to the Github Project to peek up items in the Todo column.
> > > >
> > > > And I also created a PR https://github.com/apache/pulsar/pull/17038
> to
> > > > add the PRs and issues
> > > > with `flaky-tests` label to this project automatically.
> > > >
> > > > BTW, I also have some questions about the Github Project automation.
> As
> > > > the description of
> > > > column `Review in progress, it said the PR with request changes would
> > go
> > > > to this column
> > > > automatically. But it doesn't work. I'm not sure why.
> > > > [image: image.png]
> > > >
> > > > Best,
> > > > Penghui
> > > >
> > > >
> > >
> >
>

Reply via email to