June 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[yast-devel] rspec 3.0
by Josef Reidinger 17 Dec '14

17 Dec '14

Hi, in this blog post http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3 is summary of changes in new rspec 3.0. I do not think that we will use it for SLE-12 tests, but maybe it will be used for 13.2. In general I think we should not use new syntax now, but what we can do is to not use deprecated syntax as there is already alternatives to prevent future problems. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 5

[yast-devel] who is the maintainer?
by Arvin Schnell 08 Dec '14

08 Dec '14

Hi, while reassigning yast-maintainers bugs I noticed that once again the maintainer/bugowner information is inconsistent: The content of the MAINTAINER file in git differs from the output of 'osc maintainer' or 'osc bugowner'. This leads to confusion. We had this problem before and apparently fail to solve the inconsistency long term. So I propose to drop the MAINTAINER file in git and rely on osc. Instead we can have a AUTHORS files so that people not knowing about osc can still reach the authors. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 10

[yast-devel] Yast Development after SLE 12
by Lukas Ocilka 14 Jul '14

14 Jul '14

Hi, The current Yast code that we will have in SLE 12 is partly automagically translated from YCP to kind of Ruby (also called RYCP), is still using many YCP-like methods for backward compatibility. Partly - because we have already cleaned up some pieces when touching them, following the Boy-Scout Rule [#1] and so the feel quite OK. Of course, we will not be able to cleanup everything we wanted and when SLE 12 is out, we will have to maintain the codebase for years. What we will need is the "Refactoring and Cleanup" (RAC) phase, to be a regular part of the development. Obviously, result of the RAC has to end up in SLE 12 codebase. I've already started talking with the Product Management (PM) and they are more-or-less aligned with this idea. And of course, I'd love to see the RAC in openSUSE as well. For that reason, it might make sense to develop both in the same branch as long as possible (SLE 12 GA maintenance [+ SP1 development?], openSUSE development). I'd like to improve these interconnected areas: - fewer bugs - better test coverage - better code maintainability in the future There are many open questions that need to be brainstormed before we decide and start planning, to name some: - Which parts deserve the refactoring (e.g., those that we often touch, those, that are not understandable anymore, buggy, ...)? Which are your most-favorite ones? - How deep should the refactoring be, we have to keep the current "API", but what should be considered the API as we might be the only users? - As we will have to add testcases for everything we refactor, should we also move code from "clients" and "includes" to libraries to be easier to test? - How and where to run CI tests for all supported branches? - How to measure the success? I'd love to see automatically generated metrics and code coverage. Metrics could help us to identify the most-rotten pieces. - Where and how to run automatic integration tests? Will openQA help? We could build our own installation image the same way we did it for the New Installer, testing this image automatically is just another logical step. - Additional step is to run such tests for all supported products since we have enabled users to install updates during installation - this is connected to refactoring only partly, it's essential even if we haven't refactored a single line of code A few buzzwords for the fun :) - automation (don't do manually what you don't need to do) - unification (DRYing) - standardization (use libraries, don't write it yourself) #1 http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule #2 http://martinfowler.com/articles/workflowsOfRefactoring/ Thanks for your time and I'm looking forward your ideas and opinions Bye Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 16

[yast-devel] How to Change Translations after Text Freeze
by Lukas Ocilka 04 Jul '14

04 Jul '14

Hi, Text freeze will be on July 4th, but even after that deadline, we will have an option to change a few strings. It will be used in exceptional cases only! Here's the little howto: - There needs to be a bug in Bugzilla - Change the string in Git and submit the affected package - Generate new pot file (or just change the current one) - Make sure nothing else has changed - Submit new potfile to #SVN - Assign that bug (or copy of the bug) to: Shane Wims (swims(a)novell.com) - Add Karl Eichwalder (ke(a)suse.com) to Cc And that's it! Happy potting ;)! #SVN: https://svn.opensuse.org/svn/opensuse-i18n/branches/SLE12/yast/50-pot Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 3

[yast-devel] Testing AutoYast in openQA
by Lukas Ocilka 30 Jun '14

30 Jun '14

Hi, Ludwig would like to give us a favor and will try to create some AutoYast test case in openQA. This is a great step towards continuous integration testing! Would you, please, help him to get some good AutoYast profile to start with? AutoYast documentation can be found here: (maybe a bit obsolete) http://doc.opensuse.org/projects/autoyast/ (maybe internal only) http://docserv.suse.de/documents/SLES12/SLES-autoyast/ Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 9

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 30 Jun '14

30 Jun '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-bootloader: - Zipl (6 days) https://github.com/yast/yast-bootloader/pull/109 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 27 Jun '14

27 Jun '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-ldap: - Do not add MenuButton to ButtonBox (13 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (14 days) https://github.com/yast/yast-ldap/pull/16 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 26 Jun '14

26 Jun '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-ldap: - Do not add MenuButton to ButtonBox (12 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (13 days) https://github.com/yast/yast-ldap/pull/16 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (8 days) https://github.com/yast/yast-network/pull/168 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 25 Jun '14

25 Jun '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-control-center-gnome: - ellipsize overlong icon texts and add tooltips, bnc#879959 (5 days) https://github.com/yast/yast-control-center-gnome/pull/11 Pending requests in repository yast-ldap: - Do not add MenuButton to ButtonBox (11 days) https://github.com/yast/yast-ldap/pull/17 - do not add MenuButton to ButtonBox (12 days) https://github.com/yast/yast-ldap/pull/16 Pending requests in repository yast-network: - Fixed internal error raised when cloning config in AY moduleb (7 days) https://github.com/yast/yast-network/pull/168 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0