On Wed, Jan 12, 2011 at 6:06 PM, Sven Burmeister wrote:

Am Mittwoch, 12. Januar 2011, 21:09:44 schrieb Martin Schlander:

...

== Repository planning with upcoming KDE releases - KDE:Release:46 needed? == * Need for KR46 to be discussed on the mailing list * kdepim46 continues to be available

As mentioned during the meeting I am all for having KR46 if there are people who are willing to maintain it. The reason is first of all naming. The KRxy repos are actually the (only) repos which mediate their content in an obvious manner. There is no need to have a wiki page in order to explain their content. Everybody that knows that KR45 contains KDE 4.5 will also know where to look for KDE 4.6. And having enabled that repo one will only get that KDE version and never be surprised by a major version change.

Why not just have a repository that always contains the latest stable KDE version? This would be easier for users, and would be necessary anyway if opensuse-KDE is going to participate in the tumbleweed project. Considering the overlap between the KRxy repos and what is needed for tumbleweed, I think working out how tumbleweed is going to be handled now would be better than setting up a KR46 repo only to shut it down again later if you start trying to support tumbleweed. It would be considerably less confusing to users that way. KR45 can then be quietly disabled once 4.6 is released, as planned. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

Am Donnerstag, 13. Januar 2011, 01:05:37 schrieb yamaban:

...

Why not just have a repository that always contains the latest stable KDE version? This would be easier for users, and would be necessary anyway if opensuse-KDE is going to participate in the tumbleweed project.

Whenever a new version of kde got pushed into kde:distro:factory people complained about the 'sudden' change which broke their system, I wonder what would happen if KR45 would be named KR4x already and get 4.6 once it is released, the user comments will propably look the same. So wait for 4.x.1 and hope it will be more stable? I say let people throw the switch themself, this should make it clear who took the decision to update. Problem is using KR4x would make it easy to add as target for KDE:Extra and it's buddies.

...

Considering the overlap between the KRxy repos and what is needed for tumbleweed, I think working out how tumbleweed is going to be handled now would be better than setting up a KR46 repo only to shut it down again later if you start trying to support tumbleweed. It would be considerably less confusing to users that way. KR45 can then be quietly disabled once 4.6 is released, as planned.

-Todd

A proposal for naming:

Preface: x.y - stable release, x.y-1 - Last stable release.

KDE:Release:Last - If you want to keep your system unchanged after a final x.y Release from upstream, plus home for the update-releases x.y-1.z

KDE:Release:Stable - Stable release including all update-releases x.y.z

KDE:Release:Next - WIP (work in progress) snapshots, alphas. betas, RCs for the next x.y+1 release.

Please calm down we already have a ton of repos ;-) These will clash with the KDE:Distro:(Stable|Factory) repos and create more confusion. Keeping the KR4x names is precise and easy to understand

And last but not least a warning about Stable-Releases (update-releases would be nice) on the opensuse-kde - list.

This way tumbleweed could link to KDE:Release:Stable without trouble.

Another question: the normal target-archs are oss11.2 oss11.3 (oss11.4) factory should proj-tumbleweed become such an arch to? What about proj evergreen?

Javier decided to keep building kr45 for 11.1, so you see as long as someone wants to do the job it will get done. And there is currently no plan for tumbleweed yet, for the whole 4.x cycle there was a place to get something at least close to the current upstream stable release in OBS so I am sure there will be something to push to tumbleweed on demand. Regards, Karsten -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

Am Donnerstag, 13. Januar 2011, 03:19:47 schrieb todd rme:

2011/1/12 Karsten König :

...

Am Donnerstag, 13. Januar 2011, 01:05:37 schrieb yamaban:

...

...

Why not just have a repository that always contains the latest stable KDE version? This would be easier for users, and would be necessary anyway if opensuse-KDE is going to participate in the tumbleweed project.

<snip>

And there is currently no plan for tumbleweed yet, for the whole 4.x cycle there was a place to get something at least close to the current upstream stable release in OBS so I am sure there will be something to push to tumbleweed on demand.

That is my whole point. I think it would be a good idea to set up a plan for tumbleweed now, before we start adding more repositories, rather than do it later and potentially end up removing repositories that were just added.

Why not just push KDF packages to tumbleweed from time to time? It is the most supported unsupported repo by openSUSE.

There are several changes happening both in KDE and in openSUSE at around the same time (KDE 4.6, openSUSE 11.4, tumbleweed, and evergreen). My concern is if we do a piecemeal approach we will end up with another mess of repositories like we just fixed. I think it would be better to sit down, look at everything that is happening, and make one unified plan rather than sticking stuff in as it comes. In other word, don't make a move on any of these things until we know how (or if) that move will fit into the bigger picture.

If evergreen wants to keep a certain version of KDE, they can take a static copy of STABLE or whatever repo they want, no need for an extra repo managed by the KDE people. As mentioned above, tumbleweed could get KDF from time to time and that's it. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

I think from the end-user point of view the current repo naming is a bit confusing. I vote for structure like openSUSEx.x:KDE:KDEx.x -- Regards gpe On Thursday 13 Jan 2011 06:29:36 Rajko M. wrote:

On Wednesday, January 12, 2011 08:19:47 pm todd rme wrote:

...

My concern is if we do a piecemeal approach we will end up with another mess of repositories like we just fixed.

Repo naming: The numbered repo name is in line with upstream and our way referring to particular set of KDE binaries.

Supprot: The most common question when you ask user that has problems is "What KDE version?". For me as casual helper that doesn't pay attention to every rolling repository change, having one repo that has clear reference in the name is very important. It saves me time to check repo status before I continue answering. When help is provided via IRC that makes a difference in end user experience. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

El Viernes, 14 de Enero de 2011 12:15:20 Karsten König escribió:

Am Freitag, 14. Januar 2011, 11:37:20 schrieb Gabor:

...

I think from the end-user point of view the current repo naming is a bit confusing. I vote for structure like

openSUSEx.x:KDE:KDEx.x

This violates BuildService structure, openSUSEx.y is the target here, you can't put that in the front. And we are back to KR4x with your suggestion then =)

Btw it seems javier decided for a way forward, maybe he can enlighten the list as well *nudge* ;-)

Why KDE:Release:46? - Straightforward name - Having KR45, KR46 and so on means that users aren't forced to switch to KDE 4.6.x - Dirk would use it for testing KDE tarballs instead of using his home repo, like he did with KR45, speeding up the release process of KDE tarballs. - Gives users another choice... KDE on openSUSE really shines :-) Drawbacks: - Stealing KDE:Distro:Factory users - Consuming team's time - Yet another repo, obs resource consuming All in all, I think it's positive to have KR46. Cheers, -- Javier Llorente