Hi KDE Team, great to see you guys pull the wagon! I wish you strength for the adventure ahead. On Wed, 2015-04-01 at 22:10 +0200, Raymond Wooninck wrote:

* tittiatcoke to check with openQA team who should normally write new tests for openQA

Preferably the team introducing the new setup to be tested; it's considered an integral part of the submission (of course we're all here to work this out together). A good starting point might be to get a test running already know, attempting to install Plasma 5 on a current setup and test the apps as needed. The sooner we get the basics right, the easier it will be. Don't worry about some UI changes, as those will 'just' be some screenshots / needles requiring update. That's the smallest issue.

* tittiatcoke to check with coolo and DimStar what the limit is for the liveCD

We currently have this code: def maxsize_for_package(self, package): if re.match(r'.*-image-livecd.*', package): return 999999999 # a GB stick The Live image has to fit on a 1GB stick. Cheers, Dominique

-- Dimstar / Dominique Leuenberger

On Thursday, April 02, 2015 10:27:57 AM Alberto Planas wrote:

Anyone can write test for openQA. We only need to submit the code to:

https://github.com/os-autoinst/os-autoinst-distri-opensuse

Indeed is a very good idea to make a list on tests for KDE that are runing now:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/tests /x11

https://openqa.opensuse.org/tests/54899

and start porting it to KDE5.

Basically the process is to check the logic, commit the updates and reneedle using the openQA interface.

Looking at which KDE applications are being tested, then the main issue would be to get new screenshots as that the main menu and the panel artwork would change. The logic behind it are calling the programs that will not really change name (e.g. kate, amarok, kontact). Only for systemsettings we would have to call systemsettings5 :) As that KDE is the default desktop a lot of the screenshots needs to be changed. Is this something that we need to create ourselves, or is the process here, that we adjust the logic, update github, make Plasma5 the new default and then just run the tests ? The tests that fail can then be adjusted/fixed inside the openQA interface based on the screenshots that openQA is creating ? Apologies for these questions, but I never worked with openQA to adjust needles :) Regards Raymond -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On Thursday, April 02, 2015 10:44:31 AM Raymond Wooninck wrote:

On Thursday, April 02, 2015 10:27:57 AM Alberto Planas wrote:

...

Anyone can write test for openQA. We only need to submit the code to:

Looking at which KDE applications are being tested, then the main issue would be to get new screenshots as that the main menu and the

... panel artwork

would change. The logic behind it are calling the programs that will not really change name (e.g. kate, amarok, kontact). Only for systemsettings we would have to call systemsettings5 :)

As that KDE is the default desktop a lot of the screenshots needs to be changed. Is this something that we need to create ourselves, or is

process here, that we adjust the logic, update github, make Plasma5

default and then just run the tests ? The tests that fail can then be adjusted/fixed inside the openQA interface based on the screenshots

This is good news. This means that when the change is staged by Max, the amount of change in code will be minimal. My recommendation here is something like this: * Ask coolo or lnussel for an user in http://openqa.opensuse.org that can restart jobs and can needle (select region of interest in openQA) * Before the change in TW, check the current tests running today in KDE4. * Write a couple of test for KDE4 that can be relevant for KDE5 too, but that are missing today. * Submit the tests to the opeQA tests repo: https://github.com/os-autoinst/os-autoinst-distri-opensuse In this moment the staging projects and post-integration test are going to start failing, because you provide the tests but not the asserts (needles) * Use your openQA account to create the needles and restart the KDE failing jobs until we are green again! In this moment you know most of the things about openQA, so you can start planning more test relevant only to the goals that the team have for KDE5. You can submit them after KDE5 is staged. the the new that

openQA is creating ?

Thanks to the staging projects both a good approach: KDE5 is going to broke the needles, and this is not important. The important things are (IMHO) the missing tests that are for KDE5 but we need yet to implement, in order to be sure that KDE is working as expected. So I think that a good strategy is start playing with openQA with KDE4, provide one or two more tests to really understand how it works and how to fix the test (hard to do) and provide the needles (easy to do).

Apologies for these questions, but I never worked with openQA to adjust needles :)

I really believe that this is a-ma-zing! I am sure that once the KDE team will play with openQA to see how important is to TW and openSUSE, more contributors will provide dozen of new test for systemd, the kernel, LO and more important components for the system.

Regards

Raymond

-- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

Hi there! Looks like some great progress on this front! Can we perhaps facilitate this project at the openSUSE Conference by organizing a session (and / or dev tables) dedicated to this? Let me know and we'll make it happen! Best regards, Hans de Raad Projectlead openSUSE Conference and Kolab Summit -- OpenNovations / DevHdR Van Sevenbergestraat 49 2274PK Voorburg Tel +31 6 83578847 www.hcderaad.nl On Wednesday, April 01, 2015 10:10:42 PM Raymond Wooninck wrote:

=== Meeting 1st April 2015 ===

For discussion this week:

1 Transition plan to switch TW to Plasma5 as default. When, how, etc. 2 Issues that were reported regarding Plasma5 from the community.Changes to the default setup: Application Menu, Desktop Theme, etc 3 SDDM startup issue with Breeze theme. Solution, workaround, .. ? 4 Status KDE Applications 15.04. 5 OBS repositories that will be used for Frameworks, Plasma and Applications. 6 AOB, Q&A

Decisions:

* Transition to Plasma5 as default will happen end of April (depending on the readiness of openQA) * KDE Applications 15.04 will be released for Factory/Tumblweed together with the switch to Plasma5 * Plasma5/Framework5 and Applications 15.04 will obsolete their KDE4 counterpart packages * KDE 4 as a Desktop Environment will no longer be supported/maintained for Factory/Tumbleweed after the transition. * The default menu in Plasma5 will be kicker * Breeze will be the default theme for Plasma5 * The upstream KDE menu structure will be used * The new OBS repositories will be KDE:Frameworks (for Frameworks and Plasma5), KDE:Applications (for the KDE Application releases) and KDE:Extra (for other KDE/Qt related community packages. For each one of these repos there will be an unstable variant

Action items

* Think what to do with the Update Applet (Apper/Muon) ? Or should we drop this in favor of plain YaST/zypper ? * tittiatcoke to check with openQA team who should normally write new tests for openQA * tittiatcoke to check with coolo and DimStar what the limit is for the liveCD * shumski to contact the volunteer to openSUSE'ify the Breeze iconset * shumski to look into the default browser settings

The full transcript of the meeting can be found at http:// community.opensuse.org/meetings/opensuse-kde/2015/opensuse-kde. 2015-04-01-18.00.log.html

-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org