Re: [HACKERS] No Issue Tracker - Say it Ain't So!
On Tue, Sep 29, 2015 at 6:39 PM, Josh Berkus <j...@agliodbs.com> wrote: > On 09/29/2015 03:08 PM, Merlin Moncure wrote: >> I've read this email about three times now and it's not clear at all >> to me what a issue/bug tracker brings to the table. > > Here are the problems I'd like to solve: > > 1. "Was this issue fixed in a Postgres update? Which one?" > > 2. Not losing track of minor bugs. > > 3. Having a better way to track bugs which require multi-part solutions > (e.g. multixact). > > 4. Having a place for downstream projects/packagers to report bugs. > > 5. Not answering this question ever again: "Why doesn't your project > have a bug tracker?" Merlin, I'm not sure if you are trolling me/us. I'm going to assume not and interpret the comment from the prospective of: "the current process works for those currently using the process" That may be true (I'll leave it to someone more familiar with the process to address). What that comment doesn't address is the needs of those who are not currently involved or those who are not on this email list. Just as "read the code" is an insufficient answer to a user who is looking to use a feature, "read the mailing list" is an insufficient answer to a query from a user about the state of bugs past and present. Given that, in addition to Josh's five points from an insider's perspective I would add some from an outsider's perspective: 1/ Is the issue I'm having a known bug that can be fixed by an upgrade to a more recent version, if so, which one? 2/ This project must be disorganized and/or not truly mature w/o a central tracker 3/ No hints or help on what might be an easier place to start contributing Hope that helps. -Kam Lasater @seekayel -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] No Issue Tracker - Say it Ain't So!
Hello, Last night I heard that Postgres had no issue/bug tracker. At first I thought the guy was trolling me. Seriously, how could this be. Certainly a mature open source project that is the database for a measurable percentage of the internet would have an issue tracker. Sadly, I was not being trolled. I'm new around here so I will keep the preaching to a minimum and cut right to the chase... ___It is time for an issue tracker___ Consider it a sign of success. Y'all have done a GREAT job! Searching the archives I see that this has come up before. This project is mature enough that it has graduated to needing the support of an issue tracker. At this point not having one is borderline negligent. I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably in that order). There are tens to hundreds of other great ones out there, I'm sure one of them would also work. Hopefully this feedback from a community member is helpful/useful, that was my goal in writing in, I trust my intent comes through in this email. And thanks for an awesome product :) Cheers. -Kam Lasater @seekayel
Re: [HACKERS] No Issue Tracker - Say it Ain't So!
> > I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably in > > that order). There are tens to hundreds of other great ones out there, > > I'm sure one of them would also work. > > If you install debbugs and feed it from our lists, maybe enough of us > would jump into the bandwagon enough to get it off the ground. I'm > unsure that it would work to maintain something that's too removed from > the mailing lists. Alvaro, Thanks for the suggestion. However, an issue tracker is not a replacement for mailing list(s) and vice versa. They are both necessary for success. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] No Issue Tracker - Say it Ain't So!
> > We have to use something OSS; open source projects depending on > > closed-source infra is bad news. Out of what's available, I'd actually > > choose Bugzilla; as much as BZ frustrates the heck out of me at times, > > it's the only OSS tracker that's at all sophisticated. Josh, I'm not sure I agree here on the BT needing to be OSS. That said not sure its my call :) > ... The above-referenced individuals > would be the bug tracking system curators, of course. Unless it's got > serious technical issues, the infrastructure team will do our best to > support the choice. On the other hand, some of us would likely be > involved in bug curation also. Stephen, In digging around more I found this wiki page that seems to be the closest thing to a BT: https://wiki.postgresql.org/wiki/Todo Is the curation already being done? If the contents of that wiki page were injected into a BT, would that be enough of a start? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
