Am Samstag, 8. Oktober 2011, 19:28:36 schrieb Christian Trippe:
I don't think it would make much of a difference. From my experience UpdatedApps (or better the former Backports) worked similar. There sometimes were patches to make important things like digikam work also with older distributions but it mostly was, "let's see if the factory version builds". Maybe I am wrong here and in former days it was really different. But since Martin has taken over maintainership, at least this step happens again, which was not always the case before.
So as there was only critic so far in the way he maintains KUA. I at least find it great that he has taken over the maintainership, because the situation has improved in my opinion.
Absolutely! I'm not criticising him at all – just saying that he is not the ideal maintainer for that repo. The sad thing is that without him there would be none.
I also would say that shipping the last minor upstream release as update might be a good /the best idea given the current resources.
However I also would say that the work on the KRxy repos at least to some degree causes the bad update situation you describe below. To say it once more: There is no longer a strict update policy for openSUSE you even get an agreement for only more or less cosmetic bugs, so there is no reason to not do more updates (except resources).
It felt/I thought that KRxy was left pretty much alone for most of the time, e.g. after 4.7 was released upstream.
That is in my opinion the point where we have to change. I actually see no reason, why we do not do more updates, except that the people doing most of the work seem to prefer to work on the "inofficial repos" (or only on the next version instead of official updates). If this is really the case than probably the best solution is really to ship the (final) content from KRxy as an update.
But here we should come to a clear policy. Because working on doing individual online updates for (small) bugs is not really useful, if a few weeks later there will be an update to a minor upstream release, which includes the fix. At least for 11.4 I can say that there was some discussion to go with 4.6.3? as an online update and in this situation I stopped looking for individual patches for online updates.
IMHO only the last minor release makes sense. And I do agree that backporting patches from other minor releases is time that could be spent better, but you will get the "regressions" killer argument as response. Upstream devs might be willing to work on regressions more actively if one would save them the "old bugs" reports resulting from oS packages. IMHO only major, major, major bugfixes and security fixes should be backported (that's the current situation anyway) and the rest just updated as upstream releases minor releases. The same should be the case for apps like digikam but those should include major versions. If you mark it as optional update and write something like "this is the last upstream bugfix release and offered as is" users can still decide whether to use it or not. And it's not like they would get less bugfixes compared to now. And since the original packages are still in oss, users can always roll-back. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org