FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 04-17-2008, 06:20 PM
Jeroen Roovers
 
Default Early stabilisation

On Thu, 17 Apr 2008 11:04:36 -0700
Chris Gianelloni <wolf31o2@gentoo.org> wrote:

> On Thu, 2008-04-17 at 19:38 +0200, Jeroen Roovers wrote:
> > On Thu, 17 Apr 2008 15:33:17 +0300
> > Samuli Suominen <drac@gentoo.org> wrote:
> >
> > > "It works. Do it."
> >
> > Oh by the way. This isn't directed toward you personally, but I
> > personally detest this "do it" attitude. You wouldn't say that to my
> > face, would you? (Trust me, you would regret it.)

> Seriously, we should be "doing it" much more than we should be sitting
> around patting each other on the backs. We're not here to stroke each
> other's egos. We're here to write software.

The leap from Personal Dislikes to (almost, but not quite) Calling
Slacker puzzles me. I think it's not a path that needed treading.


Kind regards,
JeR
--
gentoo-dev@lists.gentoo.org mailing list
 
Old 04-17-2008, 07:40 PM
"Santiago M. Mola"
 
Default Early stabilisation

On Thu, Apr 17, 2008 at 2:33 PM, Samuli Suominen <drac@gentoo.org> wrote:
> Thu, 17 Apr 2008 09:43:59 +0200
> Vlastimil Babka <caster@gentoo.org> 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.

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.

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.

[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: cooldwind@gmail.com
--
gentoo-dev@lists.gentoo.org mailing list
 
Old 04-17-2008, 09:51 PM
Thomas Anderson
 
Default Early stabilisation

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 <drac@gentoo.org> wrote:
> > Thu, 17 Apr 2008 09:43:59 +0200
> > Vlastimil Babka <caster@gentoo.org> 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: cooldwind@gmail.com
> --
> gentoo-dev@lists.gentoo.org mailing list
 

Thread Tools




All times are GMT. The time now is 10:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org