On Sunday 29 August 2010 20:56:36 Rahim Johnson wrote:
Will Stephenson <wstephenson <at> suse.de> writes:
This is to hammer out the details of the stable KDE 4.5 repo
Thanks for working on this! I am very interested in seeing a "Current Stable KDE Releases" repo that offers official KDE 4.x and 4.x.y releases that does *not* depend on openSUSE factory and which will *not* introduce the instability of beta/dev snapshots. Thanks for your time!
a) Naming
I don't think this should go under top level KDE: since we will have other versions. Perhaps KDE:SC:45 or KDE:Release:45?
I like the idea of KDE:Release:45. Presumably this would offer 4.5.0, and then 4.5.1 and 4.5.2 as they are officially release by KDE? Then we could have KDE:Release:46 whenever 4.6.0 is officially stable.
I vaguely counted 3.5 votes for Release, 3 for SC, and one undeterminate (Martin) ;).
c) Update frequency/policy
This is a question for the maintainers. Options:
*) On KDE bugfix release (4.5.1 etc) This seems safe but remember that the Akonadi PIM port is still planned to be released with 4.5, even if this is being pushed back. I am not sure that a major change to the PIM stack as an update is what Open-PC users want *) Arbitrary updates as decided by maintainers. This would allow 'good builds' to go out as updates without surprises like Akonadi PIM.
Sorry, I'm not a maintainer and I can't contribute to this project. But my personal opinion is that this should be a combination of both official KDE releases and updates as decided by maintainers. KDE has been quite conservative recently (as with the KDE PIM thing), so I think we can trust all their 4.x.y releases. Additionally, some really irritating bugs are sometimes fixed before the next KDE bugfix release comes out, so it might be good for the maintainers to have that option available to include bugfixes in midcycle.
I think we're mostly in agreement that "upstream releases plus selected fixes" is a workable policy then.
Another request: Would it be possible to include delta rpm patches in this repo to save openSUSE and the users a whorequestle LOT of bandwidth?
Not yet, because OBS does not yet support generating deltas. The deltas in openSUSE update repositories are still generated manually. Delta support is planned for OBS 2.2, end of year. So assuming we know a) and c) that leaves b) - implementation. Which should be done: Last Tuesday I created the project and linked the packages into it at their then latest revisions from KDE:Distro:Factory. This weekend Javier and Beineri fixed some issues, and I've just added KDE:Extras repos that build vs KR45, so from my point of view we are ready to announce this and document it. Any objections? Maintenance of the repository should only be disabling publishing (announce here), an occasional loop over all the packages with osc setlinkrev when a new upstream point release comes out, and renabling publishing, or a setlinkrev of individual packages when we fix important things. In the medium term, when we are ready to put KDE 4.6 beta in KDF, we need to coordinate copying the 4.5 sources into KR45. Javier, I assume this repo is good for your Open-PC needs? Have you created a 'permanent' repo for Open-PC images that aggregates KR45 packages? What is the status of the KDE 4.5 11.3 respin? Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org