On Thu, Apr 17, 2008 at 09:40:22PM +0200, Santiago M. Mola wrote:
> On Thu, Apr 17, 2008 at 2:33 PM, Samuli Suominen <[EMAIL PROTECTED]> wrote:
> > Thu, 17 Apr 2008 09:43:59 +0200
> >  Vlastimil Babka <[EMAIL PROTECTED]> kirjoitti:
> >
> >  > Okay. So we can just agree it's better if the maintainer tells his
> >  > reasons when opening the bug, to spare the later clarifications?
> >
> >  "It works. Do it."
> >
> 
> While I agree with you, and I think we are free to request
> stabilization before the 30 days window, I also love when people give
> details about the stabilization and not just a "do it".
> 
> Emacs team's "test plans" [1] are the better example. Thanks to them
> I'm able to save a _lot_ of time figuring out how a package works and
> which features should test.
> 
> Some details about changes since last stable are usually useful too.
> In latest wgetpaste stabilization [2] we are told that this is a
> trivial bugfix release fixing osl support, so we can just test osl
> support and skip most of other tests.
++, this really helps the testing get done quicker.
> Also, when a program needs a sample file with some obscure format, I
> really appreciate when maintainers give a URL to a sample file so I
> don't need to search for suitable files and can strictly focus on
> testing.
Agreed, the fonts team link to a page using the fonts in the package,
which makes the package trivial to test. ++ to them.
> 
> Of course, everyone could continue with the "do it" style, but keep in
> mind that adding info like I described above can save a lot of AT work
> and, as a result, make stabilization process faster.
Most of the time I see the "doit" bugs is when the package has broad
uses(i.e. coreutils and most things owned by base-system), and I
generally don't have a problem when the package has many various uses
that all had changes.
> [1] http://overlays.gentoo.org/proj/emacs/wiki/test%20plans
> [2] http://bugs.gentoo.org/show_bug.cgi?id=211894
> 
> 
> Regards,
> -- 
> Santiago M. Mola
> Jabber ID: [EMAIL PROTECTED]
> -- 
> [email protected] mailing list

Attachment: pgpTCFPZza2v9.pgp
Description: PGP signature



Reply via email to