On Wed, Apr 28, 2010 at 4:09 PM, Dimitri Fontaine
wrote:
> Stefan Kaltenbrunner writes:
>> As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe
>> the other lists in the future as well) so the workflow would look like
>> this:
>
> Well there is a WIP to use an ArchiveOpteryX
Stefan Kaltenbrunner writes:
> As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe
> the other lists in the future as well) so the workflow would look like
> this:
Well there is a WIP to use an ArchiveOpteryX based solution to replace
the archives and get rid of the artifici
On mån, 2010-04-19 at 15:37 -0400, Robert Haas wrote:
> As far as I am concerned, this is just bellyaching. I'm glad Tom
> fixes most of the bugs because otherwise we would have a lot more
> unfixed bugs. But he's not from the only one who responds to bug
> reports, and we seem to have a pretty g
On Mon, Apr 19, 2010 at 5:02 AM, Peter Eisentraut wrote:
> On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote:
>> I think we would not even need to expose the webinterface to the wider
>> community, what we probably want is something that let's us keep the
>> current workflow but provid
On Mon, Apr 19, 2010 at 11:55 AM, Kevin Grittner
wrote:
> Tom Lane wrote:
>
>> IME many of the bugs that go unanswered are non-bugs (eg #5316)
>> or inadequately described (eg #5429)
>
> Agreed.
>
>> If the goal is "make sure nothing important slips through the
>> cracks", a tracker could help.
Tom Lane wrote:
> IME many of the bugs that go unanswered are non-bugs (eg #5316)
> or inadequately described (eg #5429)
Agreed.
> If the goal is "make sure nothing important slips through the
> cracks", a tracker could help. If the goal is "100% response rate
> to pgsql-bugs submissions",
Jaime Casanova writes:
> On Sun, Apr 18, 2010 at 9:03 PM, Robert Haas wrote:
>> What is frustrating about the current process is that ~5% of the bugs don't
>> get a response. Â How are we going to fix that problem?
> that's a two side problem, while certainly there are valid bug reports
> that f
Despite all the problems with PostgreSQL's bug-tracking system or non-system,
I've found it much nicer to deal with than OpenOffice's.
I really like the fact that it's e-mail based rather than web based. Part of
the reason for that is that I have e-mail but not web access, so I can deal
with it
On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote:
> I think we would not even need to expose the webinterface to the wider
> community, what we probably want is something that let's us keep the
> current workflow but provides a minimalistic
> status/statistics/dashboard
> feature on
On sön, 2010-04-18 at 19:47 +, Greg Sabino Mullane wrote:
> > That all sounds pretty reasonable to me, though I would favor using
> > something other than Bugzilla for the tracker. I'm not really sure if
> > there's anything that I'd consider truly good out there, but I've
> > always found Bug
Stefan Kaltenbrunner wrote:
> 2a. we can simply have the tracker export a dashboard status of:
>
> *) stuff that had no reply too (which is one of the open questions)
> *) if a commit has the bug id we could have it autoclose/autotrack that
> as well
>
> 2b. for the case of "not a bug"/"added to
Stefan Kaltenbrunner wrote:
> by nagging people - if we simply had a dashboard or an email interface
> (think of the buildfarm dashboard and the status email reports it
> provides to both developers and animalowners) to make the issue more
> visible I think most of the problem of "no reply at all"
Robert Haas wrote:
On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander wrote:
On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote:
Jaime Casanova writes:
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote:
Bugzilla is the worst form of
Tom Lane wrote:
Jaime Casanova writes:
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote:
Bugzilla is the worst form of bug tracking out there, except for
all the others.
One of these days, I am going to write a @$#! bug tracker.
Robert Haas wrote:
On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner
wrote:
Jasen Betts wrote:
On 2010-04-10, Stefan Kaltenbrunner wrote:
Craig Ringer wrote:
Dave Page wrote:
This basically indicates that we need an issue tracker. There, look -
now see what you made me do :-(
Please?
On Sun, Apr 18, 2010 at 9:03 PM, Robert Haas wrote:
[...]
> What is frustrating about the current process is that ~5% of the bugs don't
> get a response. How are we going to fix that problem?
>
that's a two side problem, while certainly there are valid bug reports
that fall in the cracks, there
On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander wrote:
> On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote:
>> Jaime Casanova writes:
>>> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane
wrote:
> Bugzilla is the worst form of
Greg Sabino Mullane wrote:
Bugzilla is the worst form of bug tracking out there, except for
all the others.
flyspray isn't half bad, especially because its really simple and fairly
clean.
supports pgsql too.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
On Sun, Apr 18, 2010 at 23:14, Tom Lane wrote:
> Jaime Casanova writes:
>> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
>>> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane
>>> wrote:
Bugzilla is the worst form of bug tracking out there, except for
all the others.
>>>
>>>
Jaime Casanova writes:
> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
>> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane
>> wrote:
>>> Bugzilla is the worst form of bug tracking out there, except for
>>> all the others.
>>
>> One of these days, I am going to write a @$#! bug tracke
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas wrote:
> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane
> wrote:
>>> That all sounds pretty reasonable to me, though I would favor using
>>> something other than Bugzilla for the tracker. I'm not really sure if
>>> there's anything that I'd con
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane wrote:
>> That all sounds pretty reasonable to me, though I would favor using
>> something other than Bugzilla for the tracker. I'm not really sure if
>> there's anything that I'd consider truly good out there, but I've
>> always found Bugzilla
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> That all sounds pretty reasonable to me, though I would favor using
> something other than Bugzilla for the tracker. I'm not really sure if
> there's anything that I'd consider truly good out there, but I've
> always found Bugzilla pretty ter
On sön, 2010-04-18 at 13:12 -0400, Robert Haas wrote:
> That all sounds pretty reasonable to me, though I would favor using
> something other than Bugzilla for the tracker. I'm not really sure if
> there's anything that I'd consider truly good out there,
There isn't. Welcome to the show.
;-)
On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner
wrote:
> Jasen Betts wrote:
>>
>> On 2010-04-10, Stefan Kaltenbrunner wrote:
>>>
>>> Craig Ringer wrote:
Dave Page wrote:
> This basically indicates that we need an issue tracker. There, look -
> now see what you made me
Jasen Betts wrote:
On 2010-04-10, Stefan Kaltenbrunner wrote:
Craig Ringer wrote:
Dave Page wrote:
This basically indicates that we need an issue tracker. There, look -
now see what you made me do :-(
Please?!?
I wonder, if EDB just went ahead and set one up, would people start
using it? I
On 2010-04-10, Stefan Kaltenbrunner wrote:
> Craig Ringer wrote:
>> Dave Page wrote:
>>
>>> This basically indicates that we need an issue tracker. There, look -
>>> now see what you made me do :-(
>>
>> Please?!?
>>
>> I wonder, if EDB just went ahead and set one up, would people start
>> usin
Craig Ringer wrote:
Dave Page wrote:
This basically indicates that we need an issue tracker. There, look -
now see what you made me do :-(
Please?!?
I wonder, if EDB just went ahead and set one up, would people start
using it? I've been tempted to do it myself, but I'm not confident I can
ha
Dave Page wrote:
> This basically indicates that we need an issue tracker. There, look -
> now see what you made me do :-(
Please?!?
I wonder, if EDB just went ahead and set one up, would people start
using it? I've been tempted to do it myself, but I'm not confident I can
handle the bandwidth/h
Andy Balholm wrote:
> On Apr 9, 2010, at 5:08 AM, Robert Haas wrote:
>
>> Something is wrong with this
>> mailing list.
>
> In the week and a half that I've been subscribed to this mailing
> list, there have been several times that I received a reply to a
> message without receiving the origina
Andy Balholm wrote:
> On Apr 9, 2010, at 5:08 AM, Robert Haas wrote:
>
>> Something is wrong with this mailing list.
>
> In the week and a half that I've been subscribed to this mailing
> list, there have been several times that I received a reply to a
> message without receiving the original
On Apr 9, 2010, at 5:08 AM, Robert Haas wrote:
> Something is wrong with this
> mailing list.
In the week and a half that I've been subscribed to this mailing list, there
have been several times that I received a reply to a message without receiving
the original message. In most cases, I rece
On Fri, Apr 9, 2010 at 4:43 AM, Dave Page wrote:
> On Thu, Apr 8, 2010 at 10:23 PM, Robert Haas wrote:
>
>> BUG #5287: ispell dict erroneously returns lexeme on all prefix+suffix
>> cross products
>> BUG #5300: Bug on Mac OS X 10.6 and Postgres 8.4
>> BUG #5316: not handled error in inherit queri
On Thu, Apr 8, 2010 at 10:23 PM, Robert Haas wrote:
> BUG #5287: ispell dict erroneously returns lexeme on all prefix+suffix
> cross products
> BUG #5300: Bug on Mac OS X 10.6 and Postgres 8.4
> BUG #5316: not handled error in inherit queries
> BUG #5335: GUC value lost on exception
> BUG #4785:
On Thu, Apr 8, 2010 at 5:19 PM, Robert Haas wrote:
> It would certainly be nice if we could just have all bugs reported
> here and sort it out ourselves, but in practice that doesn't seem to
> work. When installer or pgadmin bugs are reported here, they
> typically don't get a response. Eventual
35 matches
Mail list logo
