August 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] SLE12 GIT branch?
by Ladislav Slezak 23 Sep '14

23 Sep '14

Hi all I'd like to start a discussion about creating the SLE12 branch in Git repositories. The basic questions are: - When should we create the branch? Do you need it already now? - Should we create the branches globally or should we leave that on the respective maintainers? -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 17

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

29 Aug '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-network: - Support for broadcoms multifunctional devices (14 days) https://github.com/yast/yast-network/pull/231 Pending requests in repository yast-theme: - A stub of a README. (13 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (49 days) https://github.com/yast/yast-cio/pull/7 -- 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 28 Aug '14

28 Aug '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-network: - Support for broadcoms multifunctional devices (13 days) https://github.com/yast/yast-network/pull/231 Pending requests in repository yast-theme: - A stub of a README. (12 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (48 days) https://github.com/yast/yast-cio/pull/7 -- 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 Aug '14

27 Aug '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-network: - Support for broadcoms multifunctional devices (12 days) https://github.com/yast/yast-network/pull/231 Pending requests in repository yast-theme: - A stub of a README. (11 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (47 days) https://github.com/yast/yast-cio/pull/7 -- 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] oppurtinistic refactoring
by Josef Reidinger 26 Aug '14

26 Aug '14

Hi, I would like to share with you quite nice article from Martin Fowler about oppurtinistic refactoring. I think it have some nice points which we should follow in yast development. http://martinfowler.com/bliki/OpportunisticRefactoring.html So where you see obstacles barrier for refactoring? For me it is lack of good tests, so every small refactoring need quite big effort to write tests for code. Josef -- 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 Aug '14

26 Aug '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-core: - Fixed another batch of compilation warnings. (10 days) https://github.com/yast/yast-core/pull/79 Pending requests in repository yast-network: - Support for broadcoms multifunctional devices (11 days) https://github.com/yast/yast-network/pull/231 Pending requests in repository yast-theme: - A stub of a README. (10 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (46 days) https://github.com/yast/yast-cio/pull/7 -- 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 Aug '14

25 Aug '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-core: - Fixed another batch of compilation warnings. (9 days) https://github.com/yast/yast-core/pull/79 Pending requests in repository yast-ftp-server: - [Review] Request from 'schubi2' @ 'yast/yast-ftp-server/review_140812_autoyast_configuration_module' (6 days) https://github.com/yast/yast-ftp-server/pull/8 Pending requests in repository yast-network: - Support for broadcoms multifunctional devices (10 days) https://github.com/yast/yast-network/pull/231 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (9 days) https://github.com/yast/yast-theme/pull/45 - A stub of a README. (9 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (11 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (45 days) https://github.com/yast/yast-cio/pull/7 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0