Message-ID: <4F8DCF50.4040802@gmail.com>
Date: Tue, 17 Apr 2012 16:15:12 -0400
From: Jay Levitt <jay.levitt@gmail.com>
User-Agent: Postbox 3.0.3 (Macintosh/20120304)
MIME-Version: 1.0
To: Greg Smith <greg@2ndQuadrant.com>
CC: Magnus Hagander <magnus@hagander.net>, Alex <ash@commandprompt.com>,
	Dimitri Fontaine <dimitri@2ndquadrant.fr>,
	Alvaro Herrera <alvherre@commandprompt.com>,
	Peter Eisentraut <peter_e@gmx.net>,
	Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Bug tracker tool we need
References: 
 <CA+Tgmoa75QujxzCZC+dj=0+JayGPhJD2kQMDBmbGmmq_HPgHxw@mail.gmail.com>
	<CAEYLb_VUiz57BeDy8d2gWQt_HRn9xpw83gt7MS0+wYmUopasrA@mail.gmail.com>
	<CA+TgmoZLWG=napMA-Fx4u8PTGDkY2CMz84LXAACsvhKRL+D2vg@mail.gmail.com>
	<4F84D3A0.8010808@2ndQuadrant.com>
	<CA+TgmoaN2wi85HVS-xuZkw9O6O_RmF4ovxX+=n6o2x6a1S2b-A@mail.gmail.com>
	<1334165303.25392.9.camel@vanquo.pezone.net>
	<28338.1334168965@sss.pgh.pa.us>
	<1334180206.25392.39.camel@vanquo.pezone.net>
	<CA+TgmoariJzLZ-9CfhF-Xwezk=UbmG_WUk5KydPYb8qFJzgkXw@mail.gmail.com>
	<1334350086.9019.16.camel@vanquo.pezone.net>
	<878vhyeqyq.fsf@commandprompt.com> <4F89ED6C.4030609@gmail.com>
	<87d379mwan.fsf@commandprompt.com>
	<1334540156-sup-2520@alvh.no-ip.org>
	<878vhwnjhv.fsf@hi-media-techno.com>
	<877gxf7ihf.fsf_-_@commandprompt.com> <4F8C93B2.1000503@gmail.com>
	<CABUevEw+9ZCC8eBQmWyjrmEyFFH=oBV270Hv=Cq9qPSLepehJg@mail.gmail.com>
	<4F8D6E37.5090808@gmail.com> <4F8DAF6D.7030103@2ndQuadrant.com>
In-Reply-To: <4F8DAF6D.7030103@2ndQuadrant.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Greg Smith wrote:
> On 04/17/2012 09:20 AM, Jay Levitt wrote:
>> Antispam is (in the large) a technically unsolvable
>> problem; even in the '90s, we'd see hackers start poking at our newest
>> countermeasures within the hour. GitHub is a giant target, and PG
>> probably benefits here from NOT being one.
> Everyone who deals with list moderation and spam issues around PostgreSQL
> just got a belly laugh from that comment. Hint: the PostgreSQL lists had
> already been around and therefore were being targeted by spammers for over
> ten years before GitHub even existed.

Hehe.  OK, we will have to battle this out over drinks if I ever make it to 
PGCon.. but teaser: I've bankrupted Sanford Wallace and taught the DOJ what 
spam was.

>> Pedantic note/fun fact: There was no email antispam in 1994
> I like it when Magnus really gets the details perfect when making a deadpan
> joke.

Dammit.  I *fail*.

> Anyway, back to serious talk, I believe GitHub is a dead end here because
> the "primary key" as it were for issues is a repo. A bug tracker for
> PostgreSQL would need to have issues broken down per branch and include
> information similar to the release notes for each minor point release.
> Tracking when and how a bug is backported to older versions is one hard part
> of the problem here.

That's a great point. Both GitHub and git itself have no real concept of 
releases, and can't tell you when a commit made it in.

Although.. there's some sort of new release-note functionality. Maybe I'll 
play and see if it'd be applicable here.

Jay