On Saturday 02 February 2013 08:44:14 Carl Fletcher wrote:
My real interest in this is for support purposes. As we have a significant number of users of KR49 currently and I expect they will want KR10 too. I plan to mess about a bit with apper on my sandbox, but based on what I have understood so far, I can we will be recommending Apper be removed where users venture outside the box.
Well, it is not only Apper's fault. It is that zypper has a couple of extra's build-in, which can be utilized by people that like to go outside of the box. However the target should be to improve how zypper is working with other packagemanagers and not to throw the other packagemanagers out because zypper doesn't work well with them. In the past we had also had maintainance issues with zypper/libzypp. Apper can only work with what the PackageKit-zypp backend throws at it. So we need to improve the PackageKit-zypp backend including libzypp to be better at those things and not to revert back to command line tools.
What do you think the feeling would be on implementing a rolling kde in openSUSE via standard updates. I mean stable. So no need to add R49 or whatever... it just gets pushed in via updates?
I guess you missed my earlier reply to your email. This is what we are already planning to do with 12.3 and KDE 4.10. Minor updates (e.g. 4.10.1, 4.10.2, etc) are considered as bugfix releases and can therefore be pushed through the update channel. This was already aligned and agreed with the maintenance team. Pushing however an update like KDE 4.11 through the maintenance channel would be a complete different story. This is no longer a maintainence update, but a feature release and therefore can not be pushed through the standard updates. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org