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.