blob: dddde0b46479eb268f32d33258b3c4e348ae9c78 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
<div dir="ltr">I am indeed interested in helping to establish this kind of infrastructure and I think I could reallocate some time to help with that effort. But, that would only make sense, if Mageia would adopt and use the system at the end - if it proves to be useful.<br>
Do you think that would be the case? What would be the next step? Is there some way to express a formal proposal?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/10 Guillaume Rousse <span dir="ltr"><<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Le 10/01/2013 14:18, Jochen Breuer a écrit :<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Guillame. I wasn't aware of this and did not manage to find that<br>
in the wiki. I thought the only tests performed where RPM lint checks,<br>
manual checks by the QA and some undefined checks by the maintainers.<br>
<br>
Anyhow, I assume the 'make test' is performed on the build server. Your<br>
experiences might prove me wrong, but wouldn't it be better to perform<br>
tests on a different installation?<br>
</blockquote></div>
Probably, indeed, because the environment would be closer to an actual usage environment. But this is hardly measurable.<br>
<br>
And you have to balance the added value of those additional tests with the manpower needed to setup a new test infrastructure, integrate it with current build system, and maintain it... I heard the sysadmin team was looking for volonteers, if you're interested :P<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
BOFH excuse #174:<br>
<br>
Backbone adjustment<br>
</font></span></blockquote></div><br></div>
|
