[Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features

Matt Corallo bitcoin-list at bluematt.me
Wed Jul 27 23:07:39 UTC 2011


On Thu, 2011-07-28 at 08:45 +1000, Gavin Andresen wrote:
> "A couple of bitcoins to fix a bug" sounds to me like nothing but
> trouble for whoever is in charge of awarding the bounties, but maybe
> I'm just anti-bounty because spending 2 or 3 hours and getting $30
> worth of bitcoins for fixing a bug wouldn't motivate me.

I do think it would motivate some people to fix a bug or two, though I
would say it wouldn't encourage long-term contributors, just a bunch of
hacked together patches which "fix" a bug.

> RE: road-map and bug-fix-only-releases:  Great ideas.
I know jgarzik hates the idea of branching for releases, but quite a few
projects do that, and it seems to work fairly well.  I would support the
idea of starting with 0.4 and branching for bugfixes to an 0.4 branch,
then adding new features to a head branch to be eventually called 0.5.
> 
> 
> RE: paid full-time project lead:  I arranged to get paid to work on
> bitcoin full-time before I left for Australia; more details when I get
> back week-after-next.
Awesome.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110728/e437d205/attachment.sig>


More information about the bitcoin-dev mailing list