From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NomCW-0001F8-Tu for garchives@archives.gentoo.org; Mon, 08 Mar 2010 23:17:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 162E7E0AB0; Mon, 8 Mar 2010 23:17:27 +0000 (UTC) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by pigeon.gentoo.org (Postfix) with ESMTP id 1C0C4E0972 for ; Mon, 8 Mar 2010 23:17:19 +0000 (UTC) Received: from epia.jer-c2.orkz.net (atwork-106.r-212.178.112.atwork.nl [212.178.112.106]) (authenticated bits=0) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id o28NHJ2b028761 for ; Tue, 9 Mar 2010 00:17:19 +0100 (CET) (envelope-from jer@gentoo.org) Date: Tue, 9 Mar 2010 00:17:18 +0100 From: Jeroen Roovers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Low hanging bug fruit patterns Message-ID: <20100309001718.3b2e4c0e@epia.jer-c2.orkz.net> In-Reply-To: <20100308141330.43a77611@amit.kihnet.sk> References: <4B94CC30.6020700@gentoo.org> <20100308141330.43a77611@amit.kihnet.sk> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.16.6; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by XS4ALL Virus Scanner X-Archives-Salt: 18e45fb0-2256-44f0-adb4-e2f4b8169bac X-Archives-Hash: d9d2dc5f74766cc4738491744ffed386 On Mon, 08 Mar 2010 14:13:30 +0100 R=C3=B3bert =C4=8Cer=C5=88ansk=C3=BD 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. 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). 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. jer