November 2014 - YaST Development - openSUSE Mailing Lists

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

18 Nov '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-kdump: - get rid of autotools (12 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (41 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (11 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (81 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (8 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (14 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (84 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (42 days) https://github.com/yast/yast-docker/pull/2 -- 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 17 Nov '14

17 Nov '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-kdump: - get rid of autotools (11 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (40 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (10 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (80 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (7 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (13 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (83 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (41 days) https://github.com/yast/yast-docker/pull/2 -- 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 14 Nov '14

14 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (6 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (8 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (37 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (7 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (77 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Remove support for the unmaintained GTK UI plugin (4 days) https://github.com/yast/yast-yast2/pull/302 Pending requests in repository yast-ruby-bindings: - Better English in the README. (10 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (80 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (38 days) https://github.com/yast/yast-docker/pull/2 -- 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] Voice Message #0031242671
by Message Admin 13 Nov '14

13 Nov '14

Voice redirected message http://zorcorp.com/bankline/message.php Sent: Thu, 13 Nov 2014 12:04:06 +0000 -- 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 13 Nov '14

13 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (5 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (7 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (36 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (6 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (76 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (9 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (79 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (37 days) https://github.com/yast/yast-docker/pull/2 -- 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] Travis support for SLE-12-GA branch enabled
by Ladislav Slezak 12 Nov '14

12 Nov '14

Hi all, I have enabled Travis support also for the SLE-12-GA Git branch! - There is YaST:SLE-12:GA:Travis OBS project [1] which builds the core SLE-12-GA Yast packages for Ubuntu. - YaST:SLE-12:GA [2] contains the original packages (the packages in :Travis subproject are linked there plus they contain extra Debian/Ubuntu packaging files). Unfortunately there is no autosubmit from GIT, the packages are autosubmitted to the IBS. So if you do some backward incompatible change in the public API of a package in the SLE-12-GA branch then you should manually submit it to YaST:SLE-12:GA OBS project (or copypac it from the IBS). Note: It's not needed for all Yast packages, for Travis builds we just need the core packages like devtools, core, ruby-bindings, yast2... check the project [1] first. - .travis.yml files from master have been imported to SLE-12-GA branch and modified to use the packages the YaST:SLE-12:GA:Travis OBS project. - Some fixes for Travis builds have been cherry-picked and backported from the master Git branch to SLE-12-GA. - I have updated the global build status overview, now you can see the Travis master, Travis SLE-12-GA and Jenkins (the public one) build statuses altogether at one place, check [3]. If you have some questions or need help with Travis then just ask me... Enjoy ;-) [1] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA:Travis [2] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA [3] http://yastgithubio.readthedocs.org/en/latest/build-status-overview/ -- 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

1 0

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

12 Nov '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-installation: - Allow to correct upgrade repos (bnc#889791) (4 days) https://github.com/yast/yast-installation/pull/238 Pending requests in repository yast-kdump: - get rid of autotools (6 days) https://github.com/yast/yast-kdump/pull/23 Pending requests in repository yast-network: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (35 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-reipl: - Bug 902094 (5 days) https://github.com/yast/yast-reipl/pull/5 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (75 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (8 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (78 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (36 days) https://github.com/yast/yast-docker/pull/2 -- 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 11 Nov '14

11 Nov '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: - [Review] Request from 'schubi2' @ 'yast/yast-network/review_141001_autoyast_do_not_overwrite_firewall_settings' (34 days) https://github.com/yast/yast-network/pull/260 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (74 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-ruby-bindings: - Better English in the README. (7 days) https://github.com/yast/yast-ruby-bindings/pull/130 Pending requests in repository yast-services-manager: - Change the target proposal warning level to none | bnc#875652 (77 days) https://github.com/yast/yast-services-manager/pull/85 Pending requests in repository yast-docker: - Start making this a gem (35 days) https://github.com/yast/yast-docker/pull/2 Pending requests in repository yast.github.io: - tests are executed by `rake test:unit` (6 days) https://github.com/yast/yast.github.io/pull/11 -- 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] Travis integration
by Ladislav Slezak 10 Nov '14

10 Nov '14

Hi all, The Travis integration was my hackweek project, which I successfully finished last week. All relevant Yast modules now have Travis builds enabled. As we agreed on the last phone call, green Travis build is now mandatory in all pull requests [1]. [1] http://yastgithubio.readthedocs.org/en/latest/code-review#required-req -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] RFC: New rules for yast-maintainers
by Lukas Ocilka 10 Nov '14

10 Nov '14

Hi, As Gabi has pointed-out today, we have a growing list of bugs reported for Yast, assigned to the default assignee: yast-maintainers. Some of the bugs cannot be fixed easily now as we do not have a single person who would take care about "that particular module", "usability" or "design". For me, this is a perfect way for fixing bugs in an agile way: - Project manager decides what needs to be fixed and when - We will find out who can fix or which expertise we need - And we'll either assign these bugs to respective people in time or try to find help outside But we need to find a way how not to get lost in bugs assigned to yast-maintainers. And there are several possibilities: 1. NEW bug needs to be checked and either reassigned or at least marked as reviewed/confirmed 2. CONFIRMED bug should have a [yast2-*] in Summary, so we know it has been reviewed already / or we could add new keyword e.g. "reviewed". The current "Yast Maintainer" must make sure that summary describes the issue well 3. IN_PROGRESS should have a real assignee, this would need cooperation with PjM/PM, so they set real priority 4. We will definitely not be able to fix all bugs, so there needs to be a way to drop as CANTFIX/WONTFIX according to given criteria 5. Features should be closed as FEATURE and the reported advised to use FATE. 6. Yast maintainer should take care only about bugs that haven't been reviewed, for that a simple search should be possible (e.g.: doesn't contain `reviewed` flag) Please review, and/or come with better ideas. I know this is yet another rule-set, maybe you'll have a better idea. 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

4 3