From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20130116/cffe440f/attachment-0001.html | 22 ++++++++++++++++++++++ .../attachments/20130116/cffe440f/attachment.html | 22 ++++++++++++++++++++++ 2 files changed, 44 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20130116/cffe440f') diff --git a/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment-0001.html new file mode 100644 index 000000000..dddde0b46 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment-0001.html @@ -0,0 +1,22 @@ +
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.
+Do you think that would be the case? What would be the next step? Is there some way to express a formal proposal?


2013/1/10 Guillaume Rousse <guillomovitch@gmail.com>
+
Le 10/01/2013 14:18, Jochen Breuer a écrit :

+
+Thanks Guillame. I wasn't aware of this and did not manage to find that
+in the wiki. I thought the only tests performed where RPM lint checks,
+manual checks by the QA and some undefined checks by the maintainers.
+
+Anyhow, I assume the 'make test' is performed on the build server. Your
+experiences might prove me wrong, but wouldn't it be better to perform
+tests on a different installation?
+
+Probably, indeed, because the environment would be closer to an actual usage environment. But this is hardly measurable.
+
+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
+ +
+--
+BOFH excuse #174:
+
+Backbone adjustment
+

diff --git a/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment.html b/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment.html new file mode 100644 index 000000000..dddde0b46 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20130116/cffe440f/attachment.html @@ -0,0 +1,22 @@ +
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.
+Do you think that would be the case? What would be the next step? Is there some way to express a formal proposal?


2013/1/10 Guillaume Rousse <guillomovitch@gmail.com>
+
Le 10/01/2013 14:18, Jochen Breuer a écrit :

+
+Thanks Guillame. I wasn't aware of this and did not manage to find that
+in the wiki. I thought the only tests performed where RPM lint checks,
+manual checks by the QA and some undefined checks by the maintainers.
+
+Anyhow, I assume the 'make test' is performed on the build server. Your
+experiences might prove me wrong, but wouldn't it be better to perform
+tests on a different installation?
+
+Probably, indeed, because the environment would be closer to an actual usage environment. But this is hardly measurable.
+
+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
+ +
+--
+BOFH excuse #174:
+
+Backbone adjustment
+

-- cgit v1.2.1