I could not find the functionality to make a bug block or depend on another bug. This is a useful feature in Bugzilla. I would like to see a bug report that tracks all regressions that prevent people from upgrading to KDE4. Then it would be easier and quicker to get an overview of what remains to be done.

Gentoo uses this feature successfully. It has bug reports that collect all bugs that are needed to upgrade to glibc-2.8, GCC 4.3, GCC 4.4, ....

I believe this functionality was used recently to track a bug in Solid that caused a crash when trying to verify a Solid::Predicate. See these two bugs:
https://bugs.kde.org/show_bug.cgi?id=184751
https://bugs.kde.org/show_bug.cgi?id=184749

It is likely that users do not have the needed permissions to add Depends / Blocks to bugs ( Developers have this, I can edit them )

bcooksley wrote:I believe this functionality was used recently to track a bug in

Yes indeed.

It is likely that users do not have the needed permissions to add Depends / Blocks to bugs ( Developers have this, I can edit them )

Seems like it. I can not edit dependencies. (But I did it once on bugs.gentoo.org without being a Gentoo developer.) You could help me by by adding bug #177437 to this tracker (it is a regression that has many votes and stops me from upgrading).

It appears that the bug you created is now invalid.
You could as an alternative to metabugs, is to add yourself as CC to the bug, which would allow you to follow the bugs and know when they have been resolved.

bcooksley wrote:It appears that the bug you created is now invalid.
You could as an alternative to metabugs, is to add yourself as CC to the bug, which would allow you to follow the bugs and know when they have been resolved.

Yes I know that it is marked INVALID (because someone did not like to have an overview of important regressions from KDE3 to KDE4). But I assume that it is still possible to use the metabug (adding dependencies) with the right permission? The metabug could still serve its purpose even if it is marked INVALID. (I think that just because one developer does not care about regressions does not mean that no developer does.)

Of course I know about CC and I am subscribed to many issues. But the purpose of this metabug is to specifically track important regressions from KDE3 to KDE4, not just things that should be improved in general. I know that there are thousands of open bug reports, but only a small subset of them are about things that actually do work in KDE3 but not in KDE4.

Right now I would like to have #173236 and #177437 on the list. Some people also reported miscalculations of expression like "=(2+2^2)^2" and "=2^5 * 9^2", which work fine in KDE3 (without the '='). I often use the runner for quick calculations, often for decisions involving money, so I can not upgrade until such regressions are fixed. A calculator is something that just has to work. So those problems should be listed as well.

I would recommend creating a thread in Discussions and Opinions which lists the various bugs which contain regressions, etc. to KDE 4. This way users can ensure that it is updated as needed.