[opensuse-kde] KDE 4.5 Stable Repo
This is to hammer out the details of the stable KDE 4.5 repo 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? a.a) Open-PC repo Since at some point we will no longer need KDE:SC:45, but I assume Open-PC will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can replace the symlink with its contents and Open-PC users see no interruption. b) How to implement it Fixed link revs with osc setlinkrev seem to be the obvious solution but there is a bug with this - when the linked-to repo submits to its upstream (openSUSE:Factory) and is synced back to o:F, the existing links break. I need to check this out with Adrian; Lubos has shown me how to reproduce this. In the meantime linking everything to KDF and disabling build/publish once there is a known good build should be sufficient 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. Will -- 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
On Monday 23 August 2010 08:43:15 Will Stephenson wrote:
This is to hammer out the details of the stable KDE 4.5 repo
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?
KDE:Release:45 sounds good IMO, especially considering that it also contains bits that are not part of the Software Colletion and just built on top of the 4.5 release of the KDE Platform (Amarok and K3b come to mind).
a.a) Open-PC repo
Since at some point we will no longer need KDE:SC:45, but I assume Open-PC will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can replace the symlink with its contents and Open-PC users see no interruption.
Why not let the Open-PC people maintain the 45 repo directly? Markus -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday, August 23, 2010 02:44:59 am Markus Slopianka wrote:
On Monday 23 August 2010 08:43:15 Will Stephenson wrote:
This is to hammer out the details of the stable KDE 4.5 repo
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?
KDE:Release:45 sounds good IMO, especially considering that it also contains bits that are not part of the Software Colletion and just built on top of the 4.5 release of the KDE Platform (Amarok and K3b come to mind).
a.a) Open-PC repo
Since at some point we will no longer need KDE:SC:45, but I assume Open-PC will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can replace the symlink with its contents and Open-PC users see no interruption.
Why not let the Open-PC people maintain the 45 repo directly?
Markus +1 -- upscope -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Lunes, 23 de Agosto de 2010 11:44:59 Markus Slopianka escribió:
On Monday 23 August 2010 08:43:15 Will Stephenson wrote:
This is to hammer out the details of the stable KDE 4.5 repo
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?
KDE:Release:45 sounds good IMO, especially considering that it also contains bits that are not part of the Software Colletion and just built on top of the 4.5 release of the KDE Platform (Amarok and K3b come to mind).
a.a) Open-PC repo
Since at some point we will no longer need KDE:SC:45, but I assume Open-PC will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can replace the symlink with its contents and Open-PC users see no interruption.
Why not let the Open-PC people maintain the 45 repo directly?
I would include anyone who's interested in helping out ;-) -- Javier Llorente
Mandag den 23. august 2010 08:43:15 skrev Will Stephenson:
This is to hammer out the details of the stable KDE 4.5 repo
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?
Completely agree that it shouldn't be in the top level, but "Release" sounds like a recommendation and "SC" sounds neutral. I think the name should preferably say something about the repo being a temporary thing with unsupported, barely tested packages, that are less polished, and probably *less* stable than Stable for most users. maybe KDE:Tmp:45 or something of that nature. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday 23 August 2010 18:53:28 Martin Schlander wrote:
I think the name should preferably say something about the repo being a temporary thing with unsupported, barely tested packages, that are less polished, and probably *less* stable than Stable for most users.
I thought the Open-PC guys plan to support 4.5. Personally I don't care much whether it's SC/4.5, Release/4.5, Upstream/4.5, TehAwsom/4.5, or whatever. I slightly prefer Release/4.5 but I can live with alternatives as well. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi Will, Thanks for getting this started. On Lunes, 23 de Agosto de 2010 08:43:15 Will Stephenson escribió:
This is to hammer out the details of the stable KDE 4.5 repo
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?
KDE:SC:45 sounds as it KDE:Unstable:SC should be named "KDE:SC:Unstable" :-P Anyways, I like KDE:SC:45. What about openSUSE patches in this repo?
a.a) Open-PC repo
Since at some point we will no longer need KDE:SC:45, but I assume Open- PC will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can replace the symlink with its contents and Open-PC users see no interruption.
So spins:open-pc:kde (for instance) could point at the KDE 4.5 repo and once it's EOL'ed, it could be changed to point at the appropriate repo containing the the latest stable release of KDE. In other words: spins:open-pc:kde -> KDE:SC:45 and KDE:SC:45 -> KDF (not always, only good builds). Maybe it's better to have separate repos; ie: spins:open-pc:kde45 and spins:open-pc:kde46
b) How to implement it
Fixed link revs with osc setlinkrev seem to be the obvious solution but there is a bug with this - when the linked-to repo submits to its upstream (openSUSE:Factory) and is synced back to o:F, the existing links break. I need to check this out with Adrian; Lubos has shown me how to reproduce this.
In the meantime linking everything to KDF and disabling build/publish once there is a known good build should be sufficient
OK. Why don't we vote for the name and start working on it? :-)
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.
Perhaps we could test changes like this one in K:D:F before moving to the KDE 4.5.x repo. That way we would also help with K:D:F :-) Cheers, -- Javier Llorente
On Tuesday 24 August 2010 01:00:49 Javier Llorente wrote:
Hi Will,
Thanks for getting this started.
On Lunes, 23 de Agosto de 2010 08:43:15 Will Stephenson escribió:
This is to hammer out the details of the stable KDE 4.5 repo
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?
KDE:SC:45 sounds as it KDE:Unstable:SC should be named "KDE:SC:Unstable" :-P
Anyways, I like KDE:SC:45. What about openSUSE patches in this repo?
Should be present, we are not maintaining 2 completely distinct KDE packagings, just separating publishings of one for stability.
a.a) Open-PC repo
Since at some point we will no longer need KDE:SC:45, but I assume Open-
PC
will need to still have it for the livecycle of the product, I suggest that Open-PC creates a second repo under their namespace that is a symlink (Adrian can do this) to KDE:SC:45. When we EOL KDE:SC:45, we can
replace
the symlink with its contents and Open-PC users see no interruption.
So spins:open-pc:kde (for instance) could point at the KDE 4.5 repo and once it's EOL'ed, it could be changed to point at the appropriate repo containing the the latest stable release of KDE.
In other words: spins:open-pc:kde -> KDE:SC:45 and KDE:SC:45 -> KDF (not always, only good builds). Maybe it's better to have separate repos; ie: spins:open-pc:kde45 and spins:open-pc:kde46
That's up to you.
b) How to implement it
Fixed link revs with osc setlinkrev seem to be the obvious solution but there is a bug with this - when the linked-to repo submits to its upstream (openSUSE:Factory) and is synced back to o:F, the existing links break. I need to check this out with Adrian; Lubos has shown me how to reproduce this.
In the meantime linking everything to KDF and disabling build/publish once there is a known good build should be sufficient
OK. Why don't we vote for the name and start working on it? :-)
Ok by me. My vote is for KDE:SC:45. Will -- Will Stephenson, KDE Developer, openSUSE Boosters 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
participants (5)
-
Javier Llorente -
Markus Slopianka -
Martin Schlander -
upscope -
Will Stephenson