On 9 May 2021 08:33:08 BST, Stanislav Malyshev <smalys...@gmail.com> wrote: >It is not good that our infrastructure is "hidden away in a dark >corner", and it is true that bugs needs some TLC for a while. But >Github >Issues frankly sucks big time as a bug management system. It's hard to >fault them as it's not their core business - but while it may be >adequate for a small project, I don't see how Github system could be >manageable with any serious volume.
This is my instinct as well - Github Issues seems to be adequate as a lightweight bug tracker, but how well will it scale, and how much will we miss "advanced" features like separately searchable and reportable fields and statuses? Are we better off looking for a SaaS that can provide something more full-featured - Mantis, Phabricator, Trac, Bugzilla, YouTrack, etc? It would probably be a useful exercise to mock up *how* we would use it - I'm guessing there'd be a long list of custom tags, since that's pretty much the only thing you can use for organising issues. I've seen some projects use prefixed tags like "01 - Component: XML" to simulate a hierarchy. At a glance, it seems we get as many as 100 non-spam bugs a month, so even if we don't migrate anything, we're potentially into the thousands within a couple of years. Can we do a throwaway import of a few hundred bugs to a test repo, and see what that might look like? Regards, -- Rowan Tommins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
