On Friday 04 April 2014 09:43:07 Greg KH wrote: Hello Greg,
Where will the releases be developed? In :Current? I ask as it usually takes a few days to get things settled down and working properly for a new KDE update, _and_ there are usually new packages that need to get pulled into the repo and the like.
There is a staged approach for bigger updates. e.g. KDE 4.13 will be first dropped in KDE:Distro:Factory and tested. Only when we have the confirmation that it works, the packages are moved to KDE:Current. With regards to bug fixes, we do those directly in KDE:Current as that they are just bugfixes and no new functionality is introduced. This is actually the same principle as before. bugfix releases were directly put into the respective KRXY release and for a newer version, we created a new KRX(Y+1) repository.
In other words, how will I know that it's safe to update to the packages in that repo? When they change? Or when someone says it's ok? Or when they are "published"?
When the packages are changing in that repository, then it should be safe in general to also update Tumbleweed. KDE:Current is NOT a development repository nor will there be any package in there that is not officially released. As indicated the development repository for KDE is KDE:Distro:Factory and for every new release (e.g. KDE 4.13, 4.14, etc) we are building against Factory and the current openSUSE release). Normally we have quite a number of people that are running the current openSUSE release that are testing the new release (starting with the Beta release), so once the official release is out, you could expect the update in KDE:Current after about 1 week time.
I'm all for rolling-repos, but I'd like to not break Tumbleweed user's machines if at all possible.
And we don't want to break the user machines with oS 13.1 and oS 12.3 either.:) Based on this I think that there are two ways forward, namely: 1) We stick to the old procedure. You either perform a copy of the packages (maybe a link to the packages in KDE:Current would now be better (osc linkpac -c) and then just update the link whenever you want to update the packages in Tumbleweed. 2) You keep the standard KDE packages that comes with the initial release of Tumbleweed and we start building KDE:Current against Tumbleweed. This way you do not have to worry about KDE. In my opinion the first one (and especially using the linkpac option) would be the best one. We will announce new releases in KDE:Current on the opensuse and opensuse-kde mailinglists, so that users are aware of a possibly update. At that moment you can decide to either update the links at that moment or to wait a couple of days more.
And note, I don't run KDE, so I'll just blindly keep updating the packages as you go, and I'll never know the difference, so you don't want me to be the judge of this :)
We will never ask this from you :) It is great that you are keeping Tumbleweed going and we are here to assist you in any way we can with regards to the KDE packages. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org