Hello esteemed colleagues, as many of you will know from presentations in meetings online or in the Prague office, we're planning to introduce job templates configured in YAML. After a lot of discussions, testing and tweaking, including the help from a lot of brave QAM testers, I'll lay out the plan going forward! The next deployment, due this Wednesday, August 6, will unlock saving YAML for job groups! What does this mean? The "Save" button will become available. Saving for the first time triggers migration of a job group to YAML. From there on forward the group will only be configured in YAML, and the table-based editor will be removed. Timeline of the migration The initial migration will be on an opt-in basis. Nothing will happen without the manual intervention of an actual human. The classic table-based editor will continue to function. Eventually we want to move completely to YAML. The plan is to make a hard switch in 3 months, ie. in November, and move all groups that haven't been migrated until then to YAML. What about docs? We have lovely online documentation covering this and other aspects of openQA: http://open.qa/docs/#_job_group_editor_gh2111 The YAML editor itself also has a little guide showing off the supported syntax so you don't have to know all of the details by heart from the get go. And, too, we have an API route and scripts that work with the YAML, so you might want to read up on that and see how you can take advantage of YAML even more. Regards, Cris -- Christian Dywan QA Automation Tool Developer for Software Maintenance SUSE Software Solutions Germany GmbH Maxfeldstrasse 5 90409 Nuernberg Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org