Am Samstag, 1. Oktober 2011, 07:54:48 schrieb Martin Gräßlin: > For the bugtracker I think there is a simple solution. > If a user has 4.x.y and there is a released 4.x.z with z>y don't accept the > bug report but give the user the information where to request the newer > version.
This would mean that downstream cannot fix the bug because they do not know which fix it is. And of course you have to be sure that the new minor release fixes it. > If a user has a 4.x.y and there is a 4.w.z with w>(x+1) don't accept the bug > report and give the user the information that he has to update his system > to a newer version. > I doubt we can change the way distributions release their software. As it > was mentioned in this or another thread: the distributions are always > interested in the last released version, which is not in sync with what the > developers are interested in. So as a result the user would not be able to get a fix or the info which commit fixes it from bko (bugs.kde.org) and downstream is lost but still afraid to release a minor release as official update. What about a statement of commitment from KDE devs that regressions within minor releases will get fixed before anything else across KDE? Fixing a regression is certainly in KDE's interest and downstream could be certain that they are not left alone with a regression and might consider official updates more often. > And I don't think redirecting the users to the distro's bugtracker is a > solution. It just moves the problem. That's true since it would be like somebody asking you about e.g. kdepim and fixing a bug in it. They simply cannot know each piece of software within KDE but are mainly concerned with packaging and backporting patches. Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
