| 1 |
Am 28.11.2011 17:15, schrieb Nikos Chantziaras: |
| 2 |
> On 11/28/2011 02:29 PM, Albert W. Hopkins wrote: |
| 3 |
>> On Sun, 2011-11-27 at 20:28 +0100, Andrea Conti wrote: |
| 4 |
>>> With 100% repeatability, mind you, which does raise same questions on |
| 5 |
>>> the amount of testing done before release. Yes, it's ~arch and |
| 6 |
>>> rc_parallel is explicitly marked "experimental", but it's not expected |
| 7 |
>>> to be completely and consistently broken, either. |
| 8 |
>>> |
| 9 |
>>> If that sounds like I'm ranting, it's because I just spent about an |
| 10 |
>>> hour |
| 11 |
>>> getting three machines affected by this problem back into working |
| 12 |
>>> state. |
| 13 |
>>> |
| 14 |
>>> If anyone still has it installed, it's time to sync and downgrade :) |
| 15 |
>> |
| 16 |
>> Sorry to add more to the whining but... |
| 17 |
>> |
| 18 |
>> Yes, you are in the testing tree. Yes, as a member of testing, *you* |
| 19 |
>> expect things will occasionally break, and it is *your* job to test |
| 20 |
>> things, break them, and report bugs. |
| 21 |
> |
| 22 |
> Generally true, but not when something is obviously broken. That means |
| 23 |
> not even its upstream dev bothered to test it. |
| 24 |
> |
| 25 |
> ~arch is for "we think this works, but please give it a go in case there |
| 26 |
> are problems". It's *not* for "we have no idea if this works because we |
| 27 |
> didn't even try it once". |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
Do you have any idea how much time you can spend with the kind of system |
| 32 |
testing you propose? Most companies don't do what you expect from |
| 33 |
part-time devs. You either have provide means to automate it or |
| 34 |
outsource it with very cheap labor. Otherwise it will never be done |
| 35 |
(talking from experience here). |
| 36 |
|
| 37 |
However, "dev labor" is expensive since it is limited and better spent |
| 38 |
on other issues. Automating tests for a reasonable subset of openrc's |
| 39 |
parameter space is also a tricky issue. Therefore you have to resort to |
| 40 |
cheap voluntarily provided "user labor" by means of ~arch. |
| 41 |
|
| 42 |
And it worked, didn't it? You found a bug before it entered stable. Now |
| 43 |
give yourself a pat on the shoulder for your accomplishment and go back |
| 44 |
to stable if you value your time so high that you don't want to chase bugs. |
| 45 |
|
| 46 |
Regards, |
| 47 |
Florian Philipp |
Archives