| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marco Matthies wrote: |
| 5 |
> Nathan L. Adams wrote: |
| 6 |
> |
| 7 |
>>Jory, I take issue with that. I am not ranting. I am proposing a way to |
| 8 |
>>*improve* QA. |
| 9 |
> |
| 10 |
> |
| 11 |
> Some thoughts from a humble user: |
| 12 |
> |
| 13 |
> Any improvement must neither excessively waste developer nor user time, |
| 14 |
> it is the most scarce resource. To optimize this, the common case must |
| 15 |
> be made fast, and the common case is that the bug has been truly fixed |
| 16 |
> when it has been closed. |
| 17 |
> |
| 18 |
> The person reporting the bug can reopen the bug, as he/she is in a |
| 19 |
> perfect position to test the fix. You can't have the people (developers) |
| 20 |
> who are already the busiest spend significant time recreating bugs and |
| 21 |
> testing the fix, just to find out that, yes indeed, it has been fixed. |
| 22 |
> |
| 23 |
> Sincerely, |
| 24 |
> Marco |
| 25 |
|
| 26 |
I don't think any of the devs would suggest that *any* fix should be |
| 27 |
accepted without first testing it (under the current process). If you |
| 28 |
don't believe me, submit it an ebuild and keyword it as stable on a |
| 29 |
platform that you have not tested it on. The change I'm suggesting is |
| 30 |
having either the reporter or the Team Lead verify that the 'fix' |
| 31 |
actually works. |
| 32 |
|
| 33 |
Also, in the case were the 'fix' doesn't actually fix the bug, you waste |
| 34 |
alot more development time by letting it slip through and having to |
| 35 |
'fix' it again later. So you can justify the time cost now, with time |
| 36 |
saved later. |
| 37 |
|
| 38 |
But then again, developer time *is* a very scarce resource. That's why I |
| 39 |
fielded the idea that the verification process only be required on |
| 40 |
things like Portage. |
| 41 |
|
| 42 |
Good development takes time. |
| 43 |
|
| 44 |
Nathan |
| 45 |
|
| 46 |
|
| 47 |
-----BEGIN PGP SIGNATURE----- |
| 48 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 49 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 50 |
|
| 51 |
iD8DBQFC0Cvw2QTTR4CNEQARAg7MAJ912/60YTVVPBm3AQGFy4gMweYSsgCfTfym |
| 52 |
3sQwbgylKR1GD6LllzKQDl4= |
| 53 |
=E0DJ |
| 54 |
-----END PGP SIGNATURE----- |
| 55 |
-- |
| 56 |
gentoo-dev@g.o mailing list |
Archives