[opensuse-kde] openSUSE KDE meeting 20110112
See http://en.opensuse.org/openSUSE:KDE_Meetings for futher details. == Old Action Items == * wstephenson to contact i18n team with regards to openSUSE guides. Not done but i just talked to ke yesterday and he seemed fairly chilled about 11.4 i18n. I'll ask * javier to contact Beineri with regards to the live cd listings on kde-apps. Not done * wstephenson to lead the skimming through the openfate entries. Done. == Status Report == * wstephenson: Packaged amarok 2.4.0, testing lots of patches from trueg to solve busy virtuoso, worrying about 11.4 polish and integration features being done, panicking about not doing any KNM work yet. * tittiatcoke: Unstable received it's first 4.7 trunk snapshat. KDE:Unstable:SC:kdepim46 received a couple of updates directly from git. Submitted oxygen-gtk, rekonq and bluedevil to Factory. (Not accepted yet. awaiting legal review) * krop: kdepim 4.4.9 is in kde:release:45 == Taking stock for 2011 == * We're doing farely well at packaging, bug triaging, updating etc. (bread and butter stuff) * We could do better at feature work and configuration for releases, communicating with outside world. * Cb400f complains we're not good enough at getting the relevant things into Factory quickly enough for thorough testing. Better planning and coordination needed. == 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 == tapping and Synaptiks - enable it and fix broken X default? == * We will enable touchpad tapping via Synaptiks for 11.4, with "disable while typing" set to 0.8 secs. == k3b 2.0.2 without hal requirement? == * Will Stephenson will look at the post to the mailing list. == Akonadi and mysqld running on livecd and for fresh user == * Will Stephenson will look into bnc#661844 == KPackageKit status == * KPackageKit is the default updater in 11.4. We need to test it, especially with PackageKit 0.6.11. And we need to watch bnc#637764. And we need to fix naming clash with KPK in Systemsettings vs. sw_single in YaST == Switch off nepomuk/nepomuk+strigi by default in 11.4? == * We stay with status quo of 11.3. Nepomuk stays on by default. Strigi stays off. == Q&A == * Discussion about how to name git based packages. Date or unix timestamp? No final decision. * Next meeting at 16.30 CET? mrdocs will write the list. == Action Items == * ACTION: tigerfoot think about how to execute next release cycle better (calendar, task allocation) * ACTION: tittiatcoke think about how to execute next release cycle better (calendar, task allocation) * ACTION: tittiatcoke 'enable tapping and disable while typing with 0.8 seconds' for synaptiks in kdebase4-opensuse config * ACTION: wstephenson review hal k3b 2.0.2 list * LINK: http://lists.opensuse.org/opensuse-kde/2011-01/msg00019.html * ACTION: wstephenson handle bnc#661844 * ACTION: cb400f report kpk naming clash with sw_single * ACTION: rabauke write openSUSE:KDE_11.4_packagekit * ACTION: wstephenson to contact i18n team with regards to openSUSE guides. * ACTION: javier to contact Beineri with regards to the live cd listings on kde-apps. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, 12 Jan 2011, Martin Schlander wrote: <snip>
== Q&A == * Discussion about how to name git based packages. Date or unix timestamp? No final decision. * Next meeting at 16.30 CET? mrdocs will write the list.
Word of caution here: If you decide for Date or Date-Time combo, make sure you specify the use of UTC timezone for this, else it will become ugly and confusing, real fast. So please, learn from the errors of others, and avoid this trouble beforehand, by a clear definition. Cheers, Yamaban out. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
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.
== KPackageKit status == * KPackageKit is the default updater in 11.4. We need to test it, especially with PackageKit 0.6.11. And we need to watch bnc#637764. And we need to fix naming clash with KPK in Systemsettings vs. sw_single in YaST
For testing please use and add to http://en.opensuse.org/openSUSE:KDE_11.4_packagekit Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, Jan 12, 2011 at 6:06 PM, Sven Burmeister
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
On Wed, 12 Jan 2011, todd rme wrote:
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
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. 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? Cheers, Yamaban out. -- 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
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. 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. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday, January 12, 2011 05:06:00 pm Sven Burmeister wrote:
Everybody that knows that KR45 contains KDE 4.5 will also know where to look for KDE 4.6.
+1 We all talk about versions, and repo that has version number in its name is self explanatory for anyone reading KDE or openSUSE articles. Second, it provides fallback option that is not old as one included in released openSUSE version. -- Regards, Rajko -- 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
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. -- Regards, Rajko -- 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
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* ;-) Cheers, Karsten
-- 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
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
Am I correct that once again there will be no officially supported upstream updates shipped through the regular update channels (4.6.3, 4.6.4, 4.6.5)? If so, KR46 is the obvious place for those updates. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Søndag den 16. januar 2011 17:31:05 skrev Markus Slopianka:
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
Am I correct that once again there will be no officially supported upstream updates shipped through the regular update channels (4.6.3, 4.6.4, 4.6.5)?
That is correct.
If so, KR46 is the obvious place for those updates.
All the 4.6.x releases will be built in KDE:Distro:Factory regardless of whether KR46 is created or not. Except it's undecided when KDF will go 4.7 - at 4.7beta1 or 4.7final, or somewhere inbetween. From the 11.4+1 (November 2011) perspective there's not much pressure for KDF to go to 4.7 beta early. But it might be a good idea anyway. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (9)
-
Gabor
-
Javier Llorente
-
Karsten König
-
Markus Slopianka
-
Martin Schlander
-
Rajko M.
-
Sven Burmeister
-
todd rme
-
yamaban