https://bugs.kde.org/show_bug.cgi?id=422875
--- Comment #6 from Claudius Ellsel <[email protected]> --- Unfortunately currently there are two overlapping systems to track things. Hopefully that will improve with the move to GitLab issues. From my understanding, Phabricator tasks were mostly used for actually worked on things, while feature requests (also large ones) are preferred to be tracked on Bugzilla. In my opinion, the separation between those things is pretty hard and I also don't think that it makes much sense to have this distinction. Personally I don't see big problems with huge meta bugs that probably will be open for a long time. This of course might need proper labeling and filtering when going through bug lists. And the fact that the bug is open indicates that it does indeed still have work to do (and probably still open actionably dependency bugs that are actionable). I guess it is more some kind of psychological thing whether you want to have many open bugs that might be hard to fix (like Ubuntu had with the "Make Linux the no. 1 operating system", which got closed by the way due to the success of Android). > I strongly recommend using Phabricator Tasks to track work that is large in > scope and keep Bugzilla for discrete, actionable bugs or features. Please > listen to my voice of experience here. :) I remember that in the past a Phabricator Task from me got closed because it was not thought for "users"? That is the reason why I report everything that I don't plan to work on but still consider a good improvement to Bugzilla. -- You are receiving this mail because: You are watching all bug changes.
