I think security component is special in terms of how to handle it already (e.g. not posting a test with the patch etc.) To me, handling non-security issues in GitHub and security issues in Bugzilla is OK. By nature, security issues are not open. Since one of our motivation of moving to GitHub is openness for feedback collection, security issue in Bugzilla does not matter for this motivation. Ideally, handling both in GitHub is better. But to me, rather than continuing using Bugzilla, using GitHub for non security issues sounds improvement.
-Yusuke > On Oct 5, 2020, at 12:58 PM, Fujii Hironori <fujii.hiron...@gmail.com> wrote: > > > > On Tue, Oct 6, 2020 at 12:40 AM Jonathan Bedard <jbed...@apple.com > <mailto:jbed...@apple.com>> wrote: > > That's one solution, but even that is somewhat insufficient because we don’t > want to give someone access to every security issue just to give access to a > single one. One of the solutions we’ve discussed is to migrate bugs component > by component, the security component may stay on bugzilla indefinitely. > > > I don't like this idea of using GitHub issue tracker and Bugzilla together. > Let's keep using Bugzilla for all components. > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
