https://bugs.winehq.org/show_bug.cgi?id=55142
Bug ID: 55142 Summary: Using Gitlab for Wine bug tracker Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shtetldik@gmail.com Distribution: ---
Now that Wine project is using Gitlab for managing and merging development changes, do you also plan to use it for bug tracking?
Bugzilla is cumbersome in not allowing to edit most things, not having good quality formatting, any kind of threads and so on.
https://bugs.winehq.org/show_bug.cgi?id=55142
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
--- Comment #1 from Austin English austinenglish@gmail.com --- IMO this is a non-starter until https://gitlab.com/gitlab-org/gitlab/-/issues/16225 is fixed upstream, allowing us to import our current Bugzilla issues.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #2 from Shmerl shtetldik@gmail.com --- Looks like they didn't implement some official support, but I know for example Mesa project imported Bugzilla issues into Gitlab. I wonder how it was done. I can try to find out.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #3 from Rafał Mużyło galtgendo@o2.pl ---
Bugzilla is cumbersome in not allowing to edit most things, not having good quality formatting, any kind of threads and so on.
Depending on the context, that might be a good thing. While not having to post again to correct a typo on surface looks like a good thing, it open door for major edits that may distort bug content.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #4 from Shmerl shtetldik@gmail.com --- (In reply to Rafał Mużyło from comment #3)
Bugzilla is cumbersome in not allowing to edit most things, not having good quality formatting, any kind of threads and so on.
Depending on the context, that might be a good thing. While not having to post again to correct a typo on surface looks like a good thing, it open door for major edits that may distort bug content.
Not sure I understand this. If something is distorted, you can further correct it, until it's correct. Modern bug trackers also have history of edits if anything. Immutable things on the other hand if they happened to be incorrect, stay incorrect no matter what. So I don't get what the benefit is in not being able to correct it.
https://bugs.winehq.org/show_bug.cgi?id=55142
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- I have thought about that as well, and I'm not a fan. I'm not sure gitlab has all the features bugzilla has, and I will miss those.
A few points that I think are not in Gitlab, at least not to that level: - Custom fields? - List of all duplicates? - Tags? Those are per user, and I love them to group and filter issues. - Saved filters / searches - Advanced search. Bugzilla search is really powerful, and easy to use (IMHO)
Correct me if I'm wrong. If those features are not supported in gitlab, I'd vastly prefer staying on bugzilla. Not that I'd have any say in the matter, of course.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #6 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Fabian Maurer from comment #5)
I'm not sure gitlab has all the features bugzilla has, and I will miss those.
When I last looked at it, when the GitLab move was first proposed, this was definitely not the case.
- Advanced search. Bugzilla search is really powerful, and easy to use (IMHO)
For me, this is the biggest blocker. Bugzilla search is really powerful and makes it a lot easier for Bugzilla admins to do administration.
While I can certainly see the point that GitLab might be easier for users, in my view, it will make life a lot harder for the people who have to maintain the bug tracker.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #7 from Shmerl shtetldik@gmail.com --- (In reply to Gijs Vermeulen from comment #6)
For me, this is the biggest blocker. Bugzilla search is really powerful and makes it a lot easier for Bugzilla admins to do administration.
I didn't really compare particular search capabilities, but Gitlab search isn't primitive either:
https://docs.gitlab.com/ee/user/search/advanced_search.html
https://bugs.winehq.org/show_bug.cgi?id=55142
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |bugzilla-unknown Product|Wine |WineHQ Bugzilla Severity|normal |enhancement CC| |o.dierick@piezo-forte.be
--- Comment #8 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Sorry to interrupt but this is not a bug and this discussion should be brought to the developers' mailing list or IRC.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=55142
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #9 from Zeb Figura z.figura12@gmail.com --- Besides the above, a few more points:
* The gitlab bug tracker is also far more resource-intensive than bugzilla and far less responsive. [This is true of gitlab in general, but at least the rest of it has an intended purpose that was not served by our previous tools.]
* gitlab's bulk editor doesn't seem to be as featureful as bugzilla's? I haven't tried this, but just looking at the list of what it supports, it doesn't seem to support editing as many fields, or editing from a search.
* I'm concerned about the UI of moving bugs between projects, which is going to be pretty common for Wine (e.g. moving between wine and vkd3d). In Bugzilla it's done in-place. In gitlab it apparently creates a new bug and leaves a redirect, which doesn't sound good.
Perhaps most importantly, the process of migrating bugs is not without cost; there will necessarily be some awkward adaptation necessary (consider https://gitlab.freedesktop.org/mesa/mesa/-/issues/1194... the migration has some flaws but fundamentally it's going to be necessary to reformat comments in a way that aren't maximally readable), it will have a man-hour cost in actually performing migration, and it will have a cost to those few valiant souls who are triaging bugs as they learn the new tooling.
Point being, if we are going to migrate to a different bug system, that system should not only be *as* featureful and usable as the one we're currently using, but it should offer some additional advantage, to counterbalance the very cost of migration. Three advantages were mentioned, but I find all of them to be dubious:
* This may be controversial, but I think not being able to edit comments is actually a good thing. In bug trackers where editing comments is allowed, *if* I get edit notifications, I every time have to read both the old and new versions, often multiple times, to figure out what changed. Bugzilla, lacking that feature, forces people to actually spell out their emendations explicitly. [Time was that bulletin board users used to add EDIT: tags to their posts when they edit, but I guess nobody does that anymore.]
* I have rarely seen a need for formatting in bug reports. (Like, what in this discussion is helped by formatting? The lists that Fabian and I are writing? Do we really need Markdown for those?) I also find that markdown, far from being helpful, almost always gets in my way, interpreting things like underscores, asterisks, plus and minus signs as emphasis or lists when they are not, and making things less readable instead of more. [And, of course, if I am vastly outvoted—which I often seem to be on the matter of markdown—there are patches out there that apply markdown to bugzilla. We're running a custom version anyway; we can just apply those.]
* gitlab's threading support is... barely existent; it only supports nesting threads 1 level deep. This may also be "sour grapes" of me, but I'm not sure I see what benefit thread nesting applies in a bug tracker. Also, a bug tracker is an environment where the time of a comment is generally quite important; I'd want comments to always be sorted by time, not by thread.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #10 from Austin English austinenglish@gmail.com --- (In reply to Zeb Figura from comment #9)
- This may be controversial, but I think not being able to edit comments is
actually a good thing. In bug trackers where editing comments is allowed, *if* I get edit notifications, I every time have to read both the old and new versions, often multiple times, to figure out what changed. Bugzilla, lacking that feature, forces people to actually spell out their emendations explicitly. [Time was that bulletin board users used to add EDIT: tags to their posts when they edit, but I guess nobody does that anymore.]
Wholeheartedly agreed.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #11 from Ken Sharp imwellcushtymelike@gmail.com --- The only improvement, which I'm sure could be fixed in Bugzilla, would be to properly support UTF-8 characters.
????️
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #12 from Zeb Figura z.figura12@gmail.com --- (In reply to Ken Sharp from comment #11)
The only improvement, which I'm sure could be fixed in Bugzilla, would be to properly support UTF-8 characters.
????️
I'm confused, in what way does Bugzilla not support UTF-8? I see comments with Unicode characters all the time.
I'm guessing you just tried to type some UTF-8 there and failed, but I'm interested to know what you did differently from normal.
Just to be sure... ἡ περὶ τῆς ἀληθείας θεώρια
????????????
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #13 from Zeb Figura z.figura12@gmail.com --- (In reply to Zeb Figura from comment #12)
????????????
Ah, so it probably doesn't support characters outside of the BMP correctly... that was an attempt to type Linear B, which clearly failed.
https://bugs.winehq.org/show_bug.cgi?id=55142
--- Comment #14 from Zeb Figura z.figura12@gmail.com --- (In reply to Zeb Figura from comment #13)
(In reply to Zeb Figura from comment #12)
????????????
Ah, so it probably doesn't support characters outside of the BMP correctly... that was an attempt to type Linear B, which clearly failed.
Looks like it's probably fixed in more recent Bugzilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=1253535#c78
https://bugs.winehq.org/show_bug.cgi?id=55142
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=56336
-
WineHQ Bugzilla