12/17/2023 0 Comments Bug tracker bugzillaNo way to track "Number of duplicates" or "version reported against", and they cannot be easily approximated with tags. No built-in way to communicate a "blocking" or "blocked by" relationship in GitLab CE (it's an EE only feature), and this cannot be approximated with tags. Users can't add tags to their own issue reports only developers can, which increases the burden on developers and bug triagers to keep a tidy organization because bug reporters can't help out with it. In practice, large orgs that use GitLab seem to end up having people open issues in one central repo to alleviate the above issues, resulting in issue lists that number in the thousands, making it impossible for anyone to find anything due to the lack of structure. No sub-components tags have to be used for this instead, which makes organization messy for repos/projects that currently have a lot of bug reports which are well-categorized into sub-components (e.g. Also, it doesn't solve the problem of being hard to find where to file your bug report, arguably making this problem worse because there is no longer a generic "kde" location or catch-all product like "plasmashell" where you can file something if you don't know where else it goes. A way to solve this is to put these repos into a group and only track the issues there, but then you have to disable the issues for individual repos which feels arbitrary in the cases where a bug is clearly relevant to only a particular repo. The new cloned issue has a new URL, and the original issue shows you a link to the new location, but does not automatically take you there! And if you move the issue back to its original location, still another clone is created! So visiting the original URL will show you a redirect to a redirect, potentially ad infinitum! This makes it impossible track bugs by unique, persistent URLs!īugs need to be filed against individual repos this doesn't map well to KDE software with a single logical product that is split across many repos, such as KDE PIM, Plasma, System Settings, or KWin. When an issue that was mis-filed is moved to a new location, a new clone of the issue is filed at the new location and the original issue is closed, but remains open for comments, allowing discussion to drift out of sync, and confused users can post comments in the wrong place. FWIW here is a list of blockers to migrating to GitLab issues that I have compiled recently:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |