2012/1/11 Will Stephenson
* Upstream KDE Release Schedule There is no 4.9 schedule yet (what is it with release managers and christmas?) but since KDE follows a 6-monthly cycle, add a year to the 4.7 schedule and we would have 4.9.0 on July 27 2012. So this is out for us. This means we'll probably have 4.8.4 in 12.2. Which is perfect. Having latest minor .z stable KDE release for stable openSUSE release should be our new policy, IMHO. Of course, no big version bumps, but supplying latest minor version is good.
* Factors affecting KDE in the rest of the distro Traditionally we end up reacting to these late and 'best-effort', usually because these are changes to the platform authored by redhat, adopted by openSUSE and GNOME gets them for 'free' from upstream RH, or because some other part of SUSE decides it doesn't want to take care of a feature for us any more. I'd like us to be aware of these as early as possible this time, work out the implications and the work required to turn these changes into opportunities for us rather than damage limitation exercises. ** Plymouth as bootsplash ** Systemd changes in 12.2 I don't know what these are, but I suspect they may have some influence on KDM Most of the work here will happen on their mutual integration, so influence on KDM is of low possibility (Fedora and Mint guys are using this stuff (I mean, plymouth) for some time now, AFAIK). However, there are existing KDM hiccups we need to clean up, see below.
==Want To=== These are things we would like to do as a value addition to the purely mechanistic changes pushed on us by upstream.
I have a few things in mind, to kick the discussion off I'll mention a couple here: * Quality focus 4.8, and 4.8.4 should be highly stable from upstream (changes to the platform are happening in the KDE Frameworks 5 work, so it and any 4.9 are going to be very incremental). As a distribution we can build on this with polish and targeted bugfixing based on our users' feedback. Of course things like Apper + stack, Akonadi + stack, Nepomuk + stack are big items here, but also many things that are simpler to contribute to, such as missing icons, improving translations, clarifying bad strings in the UI, cleaning up the start menu tree, setting default package selections can be done. I support this quality focus so much, guys, you can't even imagine =) Other distributions had their minor glitches removal initiatives (like Ubuntu's "papercuts" stuff), maybe it's finally time for our own? Having a really stable upstream KDE release gives us some more resources on enhancing and polishing SUSE-specific user experience, removing some "papercuts" introduced earlier. For example, KDM alone gives at least three hiccups: *No user list in current theme *No windows domain logon in current theme *Not working kcm module (bnc#267903 will soon be 5 years old, c'mon, guys, fix is rather trivial there)
* Integrate Plasma Active in openSUSE A lot of PA stuff has only been usable using git branches, but these should be mostly integrated to make a current version of PA in openSUSE doable by know. Since open-slx is our downstream, most of the work is already done. I've tried some open-slx images and Plasma Active is absolutely great, but having the ability to easily switch between three available interfaces (plasma-desktop, plasma-netbook and plasma-device) on stock openSUSE will be astonishing (if possible, of course =) ) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org