On Fri, Jun 3, 2011 at 8:42 PM, Bruce Momjian wrote:
> Just to throw out a crazy idea, there has been talk of bug ids. What if
> a thread, made up of multiple message ids, was in fact the bug id, and
> the first message in the thread (ignoring month boundaries) was the
> definitive bug id, but an
On fre, 2011-06-03 at 16:42 -0400, Bruce Momjian wrote:
> Just to throw out a crazy idea, there has been talk of bug ids. What
> if a thread, made up of multiple message ids, was in fact the bug id,
> and the first message in the thread (ignoring month boundaries) was
> the definitive bug id, but
Just to throw out a crazy idea, there has been talk of bug ids. What if
a thread, made up of multiple message ids, was in fact the bug id, and
the first message in the thread (ignoring month boundaries) was the
definitive bug id, but any of the message ids could be used to represent
the definitive
Tom Lane wrote:
> Peter Eisentraut writes:
> > That doesn't mean that better integration cannot be worked on later, but
> > this illusion that a bug tracker must have magical total awareness of
> > the entire flow of information in the project from day one is an
> > illusion and has blocked this b
Greg Stark wrote:
> On Mon, May 30, 2011 at 6:52 PM, Robert Haas wrote:
> > ?The number of people reading and replying to
> > emails on pgsql-bugs is already insufficient, perhaps because of the
> > (incorrect) perception that Tom does or will fix everything and no one
> > else needs to care. ?So
Josh Berkus wrote:
> All,
>
> Let me mention some of the reasons we as a project could use a bug
> tracker which have nothing to do with actually fixing bugs.
>
> (1) Testing: a bug tracker could be used for beta testing instead of the
> ad-hoc system I'm writing. Assuming it has the right featu
On 05/31/2011 05:41 PM, Alvaro Herrera wrote:
Excerpts from Josh Berkus's message of mar may 31 17:05:23 -0400 2011:
BTW, we talked to Debian about debbugs ages ago, and the Debian project
said that far too much of debbugs was not portable to other projects.
The good news is that the
On Wed, Jun 1, 2011 at 10:43, Dimitri Fontaine wrote:
> Alvaro Herrera writes:
>>> http://archives.beccati.org/
>>>
>>> It uses AOX (http://aox.org/) and as such is baked by a PostgreSQL
>>> database. The mails threading view is even a CTE.
>>
>> Yeah, it's great. Last time I heard, though, M
Alvaro Herrera writes:
>> http://archives.beccati.org/
>>
>> It uses AOX (http://aox.org/) and as such is baked by a PostgreSQL
>> database. The mails threading view is even a CTE.
>
> Yeah, it's great. Last time I heard, though, Mateo wasn't open to doing
> any more work on it (including fix
On tis, 2011-05-31 at 11:49 +0300, Peter Eisentraut wrote:
> On mån, 2011-05-30 at 01:30 -0400, Greg Smith wrote:
> > Greg Stark is right that Debbugs has a lot of interesting features
> > similar to the desired workflow here. It's not tied to just Debian
> > anymore; the GNU project is also usi
2011/5/31 Josh Berkus :
> All,
>
> Let me mention some of the reasons we as a project could use a bug
> tracker which have nothing to do with actually fixing bugs.
>
> (1) Testing: a bug tracker could be used for beta testing instead of the
> ad-hoc system I'm writing. Assuming it has the right fe
Excerpts from Josh Berkus's message of mar may 31 17:05:23 -0400 2011:
> BTW, we talked to Debian about debbugs ages ago, and the Debian project
> said that far too much of debbugs was not portable to other projects.
The good news is that the GNU folk proved them wrong, as evidenced
elsewhere in
Excerpts from Dimitri Fontaine's message of mar may 31 16:11:35 -0400 2011:
> Check out the following POC, which needs to get migrated into a django
> application for the upcoming new infrastructure:
>
> http://archives.beccati.org/
>
> It uses AOX (http://aox.org/) and as such is baked by a P
All,
Let me mention some of the reasons we as a project could use a bug
tracker which have nothing to do with actually fixing bugs.
(1) Testing: a bug tracker could be used for beta testing instead of the
ad-hoc system I'm writing. Assuming it has the right features, of course.
(2) User informa
Alvaro Herrera writes:
> Excerpts from Kevin Grittner's message of mar may 31 12:41:59 -0400 2011:
>> The point is that the community seems to have reached a consensus
>> that they would rather use this URL for the above message:
>>
>> http://archives.postgresql.org/message-id/20031205173035.ga1
2011/5/31 Alvaro Herrera :
> Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
>> Alvaro has also brought up the system that Debian uses which is actually
>> email based versus web based.
>
> Yeah, that's debbugs, which has been mentioned elsewhere in this thread.
I like t
On Tue, May 31, 2011 at 19:37, Peter Eisentraut wrote:
> On tis, 2011-05-31 at 14:58 +0200, Magnus Hagander wrote:
>> But sure, it can probably be improved. But what people are then
>> basically asying is that tsearch isn't good enough for searching.
>
> For one thing, there should be more structu
On 05/31/2011 11:05 AM, Alvaro Herrera wrote:
Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
Given that you have been one of the people calling for a bug tracker,
and these are the two most widely used systems available, what's wrong
with them and what else would you
On Tue, May 31, 2011 at 19:59, Joe Abbate wrote:
> On 05/31/2011 01:13 PM, Magnus Hagander wrote:
>> Just to be clear, crawling the current archives for this info is
>> probably the easiest part of the whole project. In fact, the majority
>> of the information you'd need is *already* in a postgres
On Sun, May 29, 2011 at 4:05 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> That doesn't mean that better integration cannot be worked on later, but
>> this illusion that a bug tracker must have magical total awareness of
>> the entire flow of information in the project from day one is an
>> i
On 05/31/2011 01:13 PM, Magnus Hagander wrote:
> Just to be clear, crawling the current archives for this info is
> probably the easiest part of the whole project. In fact, the majority
> of the information you'd need is *already* in a postgresql database on
> search.postgresql.org.
Does that data
Excerpts from Joshua D. Drake's message of mar may 31 12:32:43 -0400 2011:
> > Given that you have been one of the people calling for a bug tracker,
> > and these are the two most widely used systems available, what's wrong
> > with them and what else would you suggest?
>
> Just FYI, CMD uses red
On 05/31/2011 12:41 PM, Kevin Grittner wrote:
> The point is that the community seems to have reached a consensus
> that they would rather use this URL for the above message:
>
> http://archives.postgresql.org/message-id/20031205173035.ga16...@wolff.to
OK, as I said, I can still capture the mess
On tis, 2011-05-31 at 14:58 +0200, Magnus Hagander wrote:
> But sure, it can probably be improved. But what people are then
> basically asying is that tsearch isn't good enough for searching.
For one thing, there should be more structured search possibilities,
such as by date or author or subject
On Tue, May 31, 2011 at 19:10, Joe Abbate wrote:
> On 05/31/2011 12:41 PM, Kevin Grittner wrote:
>> The point is that the community seems to have reached a consensus
>> that they would rather use this URL for the above message:
>>
>> http://archives.postgresql.org/message-id/20031205173035.ga16...
On 05/31/2011 01:12 AM, Peter Eisentraut wrote:
On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
I have used RT and I found that the
web interface was both difficult to use and unwieldly for tickets
containing large numbers of messages. Maybe those those things have
been improved, but fran
Excerpts from Kevin Grittner's message of mar may 31 12:41:59 -0400 2011:
> Joe Abbate wrote:
>
> > I assume a link such as
> >
> > http://archives.postgresql.org/pgsql-bugs/2003-12/msg00046.php
> >
> > would be easier to follow than
> >
> > <20031205173035.ga16...@wolff.to>
>
> The point i
Joe Abbate wrote:
> I assume a link such as
>
> http://archives.postgresql.org/pgsql-bugs/2003-12/msg00046.php
>
> would be easier to follow than
>
> <20031205173035.ga16...@wolff.to>
The point is that the community seems to have reached a consensus
that they would rather use this URL for t
On Tue, May 31, 2011 at 12:01 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
>>> I kinda wonder why the CF app doesn't work like that, actually.
>>> (Yeah, I know the poor thread linking in the archives is an issue.)
>
>> I thought this pretty much
Hola Alvaro,
On 05/31/2011 11:38 AM, Alvaro Herrera wrote:
> I think this would be easier if you crawled the monthly mboxen instead
> of the web archives. It'd be preferable to use message-ids to identify
> messages rather than year-and-month based URLs.
I can capture the message-ids, as well as
Robert Haas writes:
> On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
>> I kinda wonder why the CF app doesn't work like that, actually.
>> (Yeah, I know the poor thread linking in the archives is an issue.)
> I thought this pretty much WAS how the CF app works, except that it's
> for patches
Excerpts from Joe Abbate's message of mar may 31 10:43:07 -0400 2011:
> I have a web crawler for a website I maintain that I could modify to
> crawl through the archives of -bugs, say from 5 Dec 2003 where the first
> bug with the new format appears, and capture the structured data
> (reference, l
On Tue, May 31, 2011 at 9:59 AM, Andrew Dunstan wrote:
> On 05/31/2011 09:33 AM, Robert Haas wrote:
>>
>> IIRC, both of them think that you should log into the web interface to
>> send emails (which, in the case of Bugzilla, don't permit replies),
>> rather than sending emails that show up in the
On Tue, May 31, 2011 at 10:02 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
>>> So in order to start a brand new bikeshed to paint on, have we even
>>> considered a very trivial workflow like letting the bugtracker
>>> actually *only* track
On 05/31/2011 04:36 AM, Magnus Hagander wrote:
> So in order to start a brand new bikeshed to paint on, have we even
> considered a very trivial workflow like letting the bugtracker
> actually *only* track our existing lists and archives. That would
> mean:
>
> * Mailing lists are *primary*, and t
Magnus Hagander wrote:
> Any patches are definitely welcome - you can find the search
> system at
> https://pgweb.postgresql.org/browser/trunk/portal/tools/search
> :-)
>
> (for the archives, you're probably most interested in
> classes/ArchiveIndexer.class.php and the sql/functions.sql file)
On Tue, May 31, 2011 at 09:36:00AM -0400, Tom Lane wrote:
> Andrew Dunstan writes:
> > On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> >> We already have a search system that works reasonably well for the
> >> archives...
>
> > I trust this weas a piece of sarcasm. I spoke to more than a few pe
"k...@rice.edu" wrote:
> maybe we can do some tweaking our search engine to improve it.
A custom dictionary to carefully add a few synonyms might go a long
way. I often need to try a number of permutations of likely words
to get relevant hits.
Including the subject line in searches, with a
On Tue, May 31, 2011 at 16:21, Kevin Grittner
wrote:
> "k...@rice.edu" wrote:
>
>> maybe we can do some tweaking our search engine to improve it.
>
> A custom dictionary to carefully add a few synonyms might go a long
> way. I often need to try a number of permutations of likely words
> to get r
Andrew Dunstan writes:
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
>> We already have a search system that works reasonably well for the
>> archives...
> I trust this weas a piece of sarcasm. I spoke to more than a few people
> at pgcon and nobody had a good word to say about the search sy
On Tue, May 31, 2011 at 09:33:33AM -0400, Robert Haas wrote:
> On Tue, May 31, 2011 at 4:12 AM, Peter Eisentraut wrote:
> > On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
> >> I have used RT and I found that the
> >> web interface was both difficult to use and unwieldly for tickets
> >> con
Robert Haas writes:
> On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
>> So in order to start a brand new bikeshed to paint on, have we even
>> considered a very trivial workflow like letting the bugtracker
>> actually *only* track our existing lists and archives. That would
>> mean:
>>
On 05/31/2011 09:33 AM, Robert Haas wrote:
IIRC, both of them think that you should log into the web interface to
send emails (which, in the case of Bugzilla, don't permit replies),
rather than sending emails that show up in the web interface.
I think you probably need to look at Bugzilla aga
On Tue, May 31, 2011 at 02:58:02PM +0200, Magnus Hagander wrote:
> On Tue, May 31, 2011 at 14:44, Andrew Dunstan wrote:
> >
> >
> > On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> >>
> >> We already have a search system that works reasonably well for the
> >> archives...
> >>
> >
> > I trust this
On Tue, May 31, 2011 at 4:36 AM, Magnus Hagander wrote:
> I get the feeling we're approaching this backwards. Wouldn't the
> normal way to do it be to define the workflow we *want*, and then
> figure out which bugtracker works for that or requires the least
> changes for that, rather than to try t
On Tue, May 31, 2011 at 4:12 AM, Peter Eisentraut wrote:
> On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
>> I have used RT and I found that the
>> web interface was both difficult to use and unwieldly for tickets
>> containing large numbers of messages. Maybe those those things have
>> be
On Tue, May 31, 2011 at 15:07, Andrew Dunstan wrote:
>
>
> On 05/31/2011 04:01 AM, Peter Eisentraut wrote:
>>
>> On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
>>>
>>> One of the conclusions the study group came to was that there should
>>> be good integration between the tracker system
On tis, 2011-05-31 at 08:44 -0400, Andrew Dunstan wrote:
>
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
> > We already have a search system that works reasonably well for the
> > archives...
> >
>
> I trust this weas a piece of sarcasm. I spoke to more than a few people
> at pgcon and nobod
On 05/31/2011 04:01 AM, Peter Eisentraut wrote:
On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
One of the conclusions the study group came to was that there should
be good integration between the tracker system and the SCM. That was
in the days before distributed SCMs were common, an
On Tue, May 31, 2011 at 14:44, Andrew Dunstan wrote:
>
>
> On 05/31/2011 06:41 AM, Magnus Hagander wrote:
>>
>> We already have a search system that works reasonably well for the
>> archives...
>>
>
> I trust this weas a piece of sarcasm. I spoke to more than a few people at
> pgcon and nobody had
On 05/31/2011 06:41 AM, Magnus Hagander wrote:
We already have a search system that works reasonably well for the archives...
I trust this weas a piece of sarcasm. I spoke to more than a few people
at pgcon and nobody had a good word to say about the search system on
the archives.
cheers
On Tue, May 31, 2011 at 11:47, Peter Eisentraut wrote:
> On tis, 2011-05-31 at 10:36 +0200, Magnus Hagander wrote:
>> I get the feeling we're approaching this backwards. Wouldn't the
>> normal way to do it be to define the workflow we *want*, and then
>> figure out which bugtracker works for that
On tis, 2011-05-31 at 10:36 +0200, Magnus Hagander wrote:
> I get the feeling we're approaching this backwards. Wouldn't the
> normal way to do it be to define the workflow we *want*, and then
> figure out which bugtracker works for that or requires the least
> changes for that, rather than to try
On mån, 2011-05-30 at 01:30 -0400, Greg Smith wrote:
> Greg Stark is right that Debbugs has a lot of interesting features
> similar to the desired workflow here. It's not tied to just Debian
> anymore; the GNU project is also using it now.
For the benefit of others, I suppose you are referring
On mån, 2011-05-30 at 22:17 -0400, Tom Lane wrote:
> Christopher Browne writes:
> > On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
> >> Based on that, and past discussions, and things we've tried in the past,
> >> and gut feeling, and so on, it looks like Request Tracker would appear
> >> to be
On Tue, May 31, 2011 at 07:08, Stefan Kaltenbrunner
wrote:
> On 05/31/2011 05:42 AM, Tom Lane wrote:
>> Kim Bisgaard writes:
>>> On 2011-05-30 04:26, Greg Stark wrote:
My biggest gripe about bugzilla was that it sent you an email with updates
to the bug but you couldn't respond to that
On Mon, May 30, 2011 at 07:42, Greg Stark wrote:
> On Sun, May 29, 2011 at 10:09 PM, Stefan Kaltenbrunner
> wrote:
>> well bugzilla has an inbound email interface as well that can both be
>> used to creande and to manipulate bugs (as in "mails that have the
>> bug-id in the subject will be added
On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
> I have used RT and I found that the
> web interface was both difficult to use and unwieldly for tickets
> containing large numbers of messages. Maybe those those things have
> been improved, but frankly if RT or Bugzilla is the best we can co
On mån, 2011-05-30 at 20:16 -0400, Christopher Browne wrote:
> My suspicion is that RT may be rather a lot heavier weight in terms of
> how it would have to affect process than people would be happy with.
>
>
> What has been pretty clearly expressed is that various of the
> developers prefer for
On mån, 2011-05-30 at 21:52 -0400, Robert Haas wrote:
> The number of people reading and replying to
> emails on pgsql-bugs is already insufficient, perhaps because of the
> (incorrect) perception that Tom does or will fix everything and no one
> else needs to care. So anything that makes it harde
On mån, 2011-05-30 at 22:43 -0400, Andrew Dunstan wrote:
> One of the conclusions the study group came to was that there should
> be good integration between the tracker system and the SCM. That was
> in the days before distributed SCMs were common, and in a commercial
> context, so I'm not sure ho
On 05/31/2011 05:42 AM, Tom Lane wrote:
> Kim Bisgaard writes:
>> On 2011-05-30 04:26, Greg Stark wrote:
>>> My biggest gripe about bugzilla was that it sent you an email with updates
>>> to the bug but you couldn't respond to that email.
>
>> Just checked bugzilla's list of features and they *n
Kim Bisgaard writes:
> On 2011-05-30 04:26, Greg Stark wrote:
>> My biggest gripe about bugzilla was that it sent you an email with updates
>> to the bug but you couldn't respond to that email.
> Just checked bugzilla's list of features and they *now* lists that as
> supported:
>> File/Modify
On Mon, May 30, 2011 at 6:52 PM, Robert Haas wrote:
> The number of people reading and replying to
> emails on pgsql-bugs is already insufficient, perhaps because of the
> (incorrect) perception that Tom does or will fix everything and no one
> else needs to care. So anything that makes it harde
On 2011-05-30 04:26, Greg Stark wrote:
My biggest gripe about bugzilla was that it sent you an email with updates to
the bug but you couldn't respond to that email.
Just checked bugzilla's list of features and they *now* lists that as supported:
File/Modify Bugs By Email
In addition to the
On 05/30/2011 09:52 PM, Robert Haas wrote:
I have used RT and I found that the
web interface was both difficult to use and unwieldly for tickets
containing large numbers of messages. Maybe those those things have
been improved, but frankly if RT or Bugzilla is the best we can come
up with then
On Mon, May 30, 2011 at 09:52:38PM -0400, Robert Haas wrote:
> On Mon, May 30, 2011 at 8:16 PM, Christopher Browne
> wrote:
> > On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
> >> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> >> > I've summarizes the main points made in the recent dis
Christopher Browne writes:
> On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>> Based on that, and past discussions, and things we've tried in the past,
>> and gut feeling, and so on, it looks like Request Tracker would appear
>> to be the next best thing to consider trying out. What do people
On 31 May 2011 11:52, Robert Haas wrote:
> I have used RT and I found that the
> web interface was both difficult to use and unwieldly for tickets
> containing large numbers of messages.
A big loud "ditto" from me on this point.
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
On Mon, May 30, 2011 at 8:16 PM, Christopher Browne wrote:
> On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
>> > I've summarizes the main points made in the recent discussion and did
>> > some minor additional research on the lists suggest
On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>
> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> > I've summarizes the main points made in the recent discussion and did
> > some minor additional research on the lists suggested by Peter and
> > Chris Browne. Anyone interested in the tra
Hi Magnus,
On 05/30/2011 08:45 AM, Magnus Hagander wrote:
> It's fine that a bug tracker *tracks* bugs. It should not control
> them. That's not how this community currently works, and a lot of
> people have said that's how they want it to stay (at least for now).
If I may belabor the point, what
Hi Greg,
On 05/29/2011 10:26 PM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* wan
On Sun, May 29, 2011 at 10:09 PM, Stefan Kaltenbrunner
wrote:
> well bugzilla has an inbound email interface as well that can both be
> used to creande and to manipulate bugs (as in "mails that have the
> bug-id in the subject will be added as a comment").
Ugh, putting it in the subject plays poo
On Mon, May 30, 2011 at 2:26 AM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want
On Mon, May 30, 2011 at 16:52, Joe Abbate wrote:
> Hi Magnus,
>
> On 05/30/2011 08:45 AM, Magnus Hagander wrote:
>> It's fine that a bug tracker *tracks* bugs. It should not control
>> them. That's not how this community currently works, and a lot of
>> people have said that's how they want it to
On Monday, May 30, 2011 07:30:37 AM Greg Smith wrote:
> Trac
While I am not a fan of trac there is a plugin for that that works reasonable
well and isn't that hard to customize if needed:
https://subtrac.sara.nl/oss/email2trac
Andres
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
On sön, 2011-05-29 at 11:05 -0400, Tom Lane wrote:
> If it has only a partial view of the set of bugs being worked on, it's
> not going to meet the goals that are being claimed for it.
>
> I don't doubt that somebody could run around and link every discussion
> about a bug into the tracker. I'm j
On Mon, May 30, 2011 at 04:26, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want t
On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> I've summarizes the main points made in the recent discussion and did
> some minor additional research on the lists suggested by Peter and
> Chris Browne. Anyone interested in the tracker, please visit
> http://wiki.postgresql.org/wiki/Tracker
On 05/29/2011 05:17 AM, Peter Eisentraut wrote:
Here is a list to choose from:
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
I turned this into a spreadsheet to sort and prune more easily; if
anyone wants that let me know, it's not terribly useful beyond what I'm
posti
Excerpts from Greg Stark's message of dom may 29 22:26:21 -0400 2011:
> My ideal bug tracker is the debian one which basically stays out of
> your way and lets you cc any message to a specific bug at
> n...@bugs.debian.org which archives that message in the bug and sends
> it to anyone listening t
On 05/30/2011 04:26 AM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want to happe
On 05/30/2011 10:57 AM, Magnus Hagander wrote:
> The case I want to avoid is (a). And if it's possible to make (b) just
> be the -hackers mailinglist and putting a keyword in the right place,
Did you mean the -bugs mailing list?
On the subject of keywords, considering Robert's suggestion to
"Asso
On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
> Anyone interested in the tracker, please visit
> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
> feedback/input.
I think this illustrates exactly what we *don't* want to happen with a
bug tracker. We want the discussion to sta
On 05/29/2011 02:01 PM, Stefan Kaltenbrunner wrote:
> feel free to reuse/edit the page as you like it(I have just removed the
> notice) - the "don't edit" thingy was added because people started to
> find the page via google (while searching for a tracker/bugreporting
> tool) and considered it offi
On 05/29/2011 05:47 PM, Joe Abbate wrote:
> Hi Tom,
>
> On 05/29/2011 11:05 AM, Tom Lane wrote:
>> In the end, I think that requests for a tracker mostly come from people
>> who are not part of this community, or at least not part of its mailing
>> lists (which is about the same thing IMO).
>
> I
Hi Tom,
On 05/29/2011 11:05 AM, Tom Lane wrote:
> In the end, I think that requests for a tracker mostly come from people
> who are not part of this community, or at least not part of its mailing
> lists (which is about the same thing IMO).
I think that's a bit harsh. I assume you consider GSM a
Peter Eisentraut writes:
> That doesn't mean that better integration cannot be worked on later, but
> this illusion that a bug tracker must have magical total awareness of
> the entire flow of information in the project from day one is an
> illusion and has blocked this business for too long IMO.
On sön, 2011-05-29 at 03:23 +, Greg Sabino Mullane wrote:
> My own bare bones wish list for such a tracker is:
>
> * Runs on Postgres
> * Has an email interface
I will add
* Free/open source software
to that.
Here is a list to choose from:
http://en.wikipedia.org/wiki/Comparison_of_issue_t
On sön, 2011-05-29 at 00:04 -0400, Tom Lane wrote:
> Many, many, many bug issues are not associated with a bug report
> submitted through the web interface. People mail stuff to pgsql-bugs
> manually, or issues turn up in threads on other lists. If a tracker
> can only find things submitted throu
On 05/29/2011 06:04 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Sat, May 28, 2011 at 11:23 PM, Greg Sabino Mullane
>> wrote:
>>> My own bare bones wish list for such a tracker is:
>>>
>>> * Runs on Postgres
>>> * Has an email interface
>>>
>>> Make no mistake, whichever we choose, the care o
Brendan Jurd writes:
> On 29 May 2011 14:04, Tom Lane wrote:
>> Anything that even pretends to be a bug tracker will do that. The
>> real question is, who is going to keep it up to date? GSM has the
>> right point of view here: we need at least a couple of people who
>> are willing to invest su
On 29 May 2011 14:04, Tom Lane wrote:
> Anything that even pretends to be a bug tracker will do that. The
> real question is, who is going to keep it up to date? GSM has the
> right point of view here: we need at least a couple of people who
> are willing to invest substantial amounts of time, o
On Sun, May 29, 2011 at 12:04 AM, Tom Lane wrote:
>> 1. Given a bug number, find the pgsql-bugs emails that mention it in
>> the subject line. Note that the archives would actually MOSTLY do
>> this ,but for the stupid month-boundary problem which we seem unable
>> to fix despite having some of t
Robert Haas writes:
> On Sat, May 28, 2011 at 11:23 PM, Greg Sabino Mullane
> wrote:
>> My own bare bones wish list for such a tracker is:
>>
>> * Runs on Postgres
>> * Has an email interface
>>
>> Make no mistake, whichever we choose, the care of feeding of such a
>> beast will require some p
On Sat, May 28, 2011 at 11:23 PM, Greg Sabino Mullane wrote:
> My own bare bones wish list for such a tracker is:
>
> * Runs on Postgres
> * Has an email interface
>
> Make no mistake, whichever we choose, the care of feeding of such a
> beast will require some precious resources in time from at l
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> well that is rather basic functionality of a tracker software and i
> would expect those to be a given, but I don't think that is where the
> problems are with implementing a tracker for postgresql.org...
Right, the problem has been the luk
98 matches
Mail list logo
