On Tue, 24 Jun 2014 09:51:41 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
Hi,
Today we have an outage of the Yast Jenkins node because of No space
left on device. This is a virtual machine maintained by a team member
(including scripts around). It's not the first time this node has died
On Thu, Jun 12, 2014 at 04:30:06PM +0200, Lukas Ocilka wrote:
- 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?
Every module I have seen has code that needs refactoring.
-
Dne 13.6.2014 15:16, Martin Vidner napsal(a):
Developer happiness matters to me, but it is hard to quantify. I
really enjoyed the progress spreadsheet we had for YCP Killer, and I
think it is important to find a meaningful metric and see it
improving as we work together. So the most important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.06.2014 18:17, schrieb Martin Vidner:
On Thu, Jun 12, 2014 at 04:30:06PM +0200, Lukas Ocilka wrote:
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
On Fri, 13 Jun 2014 15:16:52 +0200
Martin Vidner mvid...@suse.cz wrote:
On Thu, Jun 12, 2014 at 05:02:24PM +0200, Josef Reidinger wrote:
On Thu, 12 Jun 2014 16:30:06 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
[Ruby YCP - answered in a separate mail]
What we will need is the
Dne 12.6.2014 16:30, Lukas Ocilka napsal(a):
What we will need is the Refactoring and Cleanup (RAC) phase, to be a regular
part
of the development.
Great! That step was always missing in the Yast development.
- Which parts deserve the refactoring (e.g., those that we often touch,
those,
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
On Tue, 24 Jun 2014 15:00:11 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
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
On Tue, 24 Jun 2014 15:00:11 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
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
Josef Reidinger wrote:
On Tue, 24 Jun 2014 15:00:11 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
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
Hi Ludwig,
that's an great idea !!!
We can try it together. Just call me when you have time.
Greetings
Stefan
Am 24.06.2014 15:51, schrieb Ludwig Nussel:
Josef Reidinger wrote:
On Tue, 24 Jun 2014 15:00:11 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
Ludwig would like to give us a favor
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
12 matches
Mail list logo
