| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How can I check the treatment of bug fixes? |
| Date: | 2011-05-28 09:45:35 |
| Message-ID: | 4DE0C43F.5080607@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/28/2011 05:47 AM, MauMau wrote:
> From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
>> On fre, 2011-05-27 at 13:55 -0400, Robert Haas wrote:
>>> Also, I think it's about time we got ourselves some kind of bug
>>> tracker. I have no idea how to make that work without breaking
>>> workflow that works now, but a quick survey of my pgsql-bugs email
>>> suggests that this is far from the only thing slipping through the
>>> cracks.
>>
>> The problem is finding a usable bug tracking software.
>
> I think JIRA is very good. Almost all projects in Apache Software
> Foundation (ASF) including Tomcat, Hadoop, Apache HTTP server, use JIRA.
> With JIRA, we can know various counts such as the number of bugs per
> major/minor release, not-fixed bugs, new features in each major release,
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...
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2011-05-28 10:02:09 | Re: How can I check the treatment of bug fixes? |
| Previous Message | nil nil | 2011-05-28 08:53:54 | install softwares |