| 1 |
On Thu, Apr 17, 2008 at 2:33 PM, Samuli Suominen <drac@g.o> wrote: |
| 2 |
> Thu, 17 Apr 2008 09:43:59 +0200 |
| 3 |
> Vlastimil Babka <caster@g.o> kirjoitti: |
| 4 |
> |
| 5 |
> > Okay. So we can just agree it's better if the maintainer tells his |
| 6 |
> > reasons when opening the bug, to spare the later clarifications? |
| 7 |
> |
| 8 |
> "It works. Do it." |
| 9 |
> |
| 10 |
|
| 11 |
While I agree with you, and I think we are free to request |
| 12 |
stabilization before the 30 days window, I also love when people give |
| 13 |
details about the stabilization and not just a "do it". |
| 14 |
|
| 15 |
Emacs team's "test plans" [1] are the better example. Thanks to them |
| 16 |
I'm able to save a _lot_ of time figuring out how a package works and |
| 17 |
which features should test. |
| 18 |
|
| 19 |
Some details about changes since last stable are usually useful too. |
| 20 |
In latest wgetpaste stabilization [2] we are told that this is a |
| 21 |
trivial bugfix release fixing osl support, so we can just test osl |
| 22 |
support and skip most of other tests. |
| 23 |
|
| 24 |
Also, when a program needs a sample file with some obscure format, I |
| 25 |
really appreciate when maintainers give a URL to a sample file so I |
| 26 |
don't need to search for suitable files and can strictly focus on |
| 27 |
testing. |
| 28 |
|
| 29 |
Of course, everyone could continue with the "do it" style, but keep in |
| 30 |
mind that adding info like I described above can save a lot of AT work |
| 31 |
and, as a result, make stabilization process faster. |
| 32 |
|
| 33 |
[1] http://overlays.gentoo.org/proj/emacs/wiki/test%20plans |
| 34 |
[2] http://bugs.gentoo.org/show_bug.cgi?id=211894 |
| 35 |
|
| 36 |
|
| 37 |
Regards, |
| 38 |
-- |
| 39 |
Santiago M. Mola |
| 40 |
Jabber ID: cooldwind@×××××.com |
| 41 |
-- |
| 42 |
gentoo-dev@l.g.o mailing list |
Archives