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 03-09-2010, 05:24 PM
Róbert Čerňanský
 
Default Low hanging bug fruit patterns

On Tue, 9 Mar 2010 00:17:18 +0100
Jeroen Roovers <jer@gentoo.org> wrote:

> On Mon, 08 Mar 2010 14:13:30 +0100
> Róbert Čerňanský <hslists2@zoznam.sk> wrote:
>
> > - Minor version bumps (After examination what upstream changed and
> > after confirmation with mantainer, if any.)
>
> The stuff you put in brackets is exactly the sort of stuff that
> tends to make version bumps hard to fix.
>
> You would first have to determine what major/minor means, on a per
> package-version basis, so these aren't really as trivial to fix as
> (non) package maintainer as a "minor version change" might suggest.

Yes, one needs to be carefull when doing even "minor" version bump. And
after examination of changes one can decide to do the bump or leave it
because it looks too risky. I'm sure there are upstream releases that
contains only bug fixes and it can be relatively easy determined by
looking into NEWS, Changelog or similar files.

After all, the examination should not exceed 1 day of effort (Sebastian
wrote that it should not "take days" to fix). So if we say that 1 day
is still less than "days" then I think it is plenty of time to examine
upstream changes. But maybe 1 day is too much for "low hanging fruits"
so let's say 2 hours is acceptable. In that time it should be possible
to fully examine changes. Which means read the changelogs, do some
internet search (upstream and other distros bugzillas) and even take a
peek to the source code.

> Also, any version bump is a splendid occasion on which to revise the
> ebuild (introduce missing features, check for novel QA issues, move up
> an EAPI to cut out a few build phases, review COPYING to make sure
> the LICENSE variable is still OK, figure out that one slight syntax
> change might serve to fix a compilation error with a
> newer-toolchain-than-you-use).

It still can be done at another time after bump; which is maybe even
better because it could be easily distinguished whether potencial new
bugs were caused by the bump or by ebuild enhancement changes.

Also I think that the overall quality of a package is increased if it
is "just" bumped to the new minor/bugfix upstream release and ebuild
stays at the same quality level as before. Compared to staying at the
older upstream version and also with the same ebuild because nobody has
time to do bump with ebuild enhacement.

> So I generally don't regard a version bump as a low hanging fruit,
> as you might end up painfully ignoring the wasps' nest hanging
> directly beside it.

Cenrtailny not in general. So let's say it is low hanging fruit at
which you have to stare for a while and look at it from all sides
before you pick it up. ;-)

Robert


--
Robert Cernansky
E-mail: hslists2@zoznam.sk
Jabber: hs@jabber.sk
 
Old 03-09-2010, 10:17 PM
Duncan
 
Default Low hanging bug fruit patterns

Jeroen Roovers posted on Tue, 09 Mar 2010 00:17:18 +0100 as excerpted:

> I generally don't regard a version bump as a low hanging fruit, as you
> might end up painfully ignoring the wasps' nest hanging directly beside
> it.

FWIW, that's definitely sig/fortune material! =:^)

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
 

Thread Tools




All times are GMT. The time now is 09:27 PM.

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