Re: [HACKERS] No Issue Tracker - Say it Ain't So!

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. In my opinion, this thread is about a bug tracker, not a patch tracker. We already have a patch tracking system which works very well. (We are not

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/29/2015 03:46 PM, Tom Lane wrote: Alvaro Herrera writes: 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. In my opinion, this thread is about a bug tracker, not a

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 30, 2015 at 2:16 AM, Alvaro Herrera wrote: > > > That's a very good point. I think Github and other sites are already > blocked in countries like India and Cuba. Github is not blocked in India and was never as far as I know. Well our government recently

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Seems to me that there are a bunch of agendas here. I read about not wanting to be trapped into a proprietary system. You can be trapped in any software you depend upon. Compilers, Platforms, SCM, issue tracking are all places to be trapped. Postgres and Postgresql have been around a very

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 2015-09-29 13:27:15 -0400, Tom Lane wrote: > Corey Huinker writes: > >>> And they'd sure love to be in charge of our code repo. > > >> Mh - i'm not a native speaker. I didn't understand this line. > > > Tom was saying that the JIRA/Atlassian people would happily

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Andres Freund writes: > On 2015-09-29 13:27:15 -0400, Tom Lane wrote: >> Not that so much as that the gitlab code really wants to be connected up >> to our code repo. That makes complete sense in terms of its goals as >> stated by Torsten upthread, namely to be a git repo

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

> > > And they'd sure love to be in charge of our code repo. >> > > Mh - i'm not a native speaker. I didn't understand this line. > > Tom was saying that the JIRA/Atlassian people would happily volunteer to host our code repository for no cost (in money) to us. The implication being that they have

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Corey Huinker writes: >>> And they'd sure love to be in charge of our code repo. >> Mh - i'm not a native speaker. I didn't understand this line. > Tom was saying that the JIRA/Atlassian people would happily volunteer to > host our code repository for no cost (in money)

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 2015-09-29 13:40:28 -0400, Tom Lane wrote: > Andres Freund writes: > > I don't have any opinion WRT gitlab, but I'm fairly certain it'd be > > unproblematic to configure automatic mirroring into it from > > gitmaster. > > I think you missed my point: gitlab would then

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Andres Freund writes: > On 2015-09-29 13:40:28 -0400, Tom Lane wrote: >> I think you missed my point: gitlab would then believe it's in charge of, >> eg, granting write access to that repo. We could perhaps whack it over >> the head till it only does what we want and not ten

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/29/2015 07:25 AM, Merlin Moncure wrote: On Wed, Sep 23, 2015 at 1:18 PM, Kam Lasater wrote: 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Stephen Frost writes: > * Jim Nasby (jim.na...@bluetreble.com) wrote: >> 2 years ago is when they first released the enterprise edition, >> which according to [1] had "The most important new feature is that >> you can now add members to groups of projects." > It needed a lot

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 2015-09-28 09:41:18 -0700, David Fetter wrote: > Since you're convinced that this is an unqualified win, please put > together a project plan for switching from our current system to > Github. Err, no. That's a waste of all our time. It has been stated pretty clearly in this thread by a

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Mon, Sep 28, 2015 at 07:14:40PM +0300, YUriy Zhuravlev wrote: > On Monday 28 September 2015 08:23:46 David Fetter wrote: > > They may well be, but until we decide it's worth the switching > > costs to move to a totally different way of doing things, that > > system will stay in place. > Until

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/28/2015 05:50 AM, YUriy Zhuravlev wrote: On Thursday 24 September 2015 12:10:07 Ryan Pedela wrote: Kam Lasater wrote: 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Mon, Sep 28, 2015 at 03:50:29PM +0300, YUriy Zhuravlev wrote: > On Thursday 24 September 2015 12:10:07 Ryan Pedela wrote: > > Kam Lasater wrote: > > > I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably > > > in that order). There are tens to hundreds of other great ones > > > out

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Monday 28 September 2015 08:23:46 David Fetter wrote: > They may well be, but until we decide it's worth the switching costs > to move to a totally different way of doing things, that system will > stay in place. Until we decide we're wasting time >Neither magic wands nor a green field project

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Jim Nasby writes: > On 9/28/15 11:43 AM, Andres Freund wrote: >> It has been stated pretty clearly in this thread by a number of senior >> community people that we're not going to use a closed source system. > GitLab OTOH is released under a MIT license, so it is an

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Mon, Sep 28, 2015 at 4:09 PM, Jim Nasby wrote: > On 9/28/15 11:43 AM, Andres Freund wrote: > >> On 2015-09-28 09:41:18 -0700, David Fetter wrote: >> >>> Since you're convinced that this is an unqualified win, please put >>> together a project plan for switching from

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/28/2015 03:40 PM, Alvaro Herrera wrote: Tom Lane wrote: Now, running gitlab on community-owned hardware would potentially be an option, if we find gitlab attractive from a functionality standpoint. The question I'd have about that is whether it has a real development community, or is

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Josh Berkus writes: > The infra team seems to be good with debbugs, and several committers > seem to like it, why not go with it? It certainly seems like debbugs is the proposal to beat at this point. In the end though, what matters is somebody doing the dogwork to make it

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/28/15 5:34 PM, Tom Lane wrote: Now, running gitlab on community-owned hardware would potentially be an option, if we find gitlab attractive from a functionality standpoint. The question I'd have about that is whether it has a real development community, or is open-source in name only. If

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/28/15 6:06 PM, Tom Lane wrote: Josh Berkus writes: The infra team seems to be good with debbugs, and several committers seem to like it, why not go with it? It certainly seems like debbugs is the proposal to beat at this point. In the end though, what matters is

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 29/09/15 11:54, Joshua D. Drake wrote: On 09/28/2015 03:40 PM, Alvaro Herrera wrote: Tom Lane wrote: Now, running gitlab on community-owned hardware would potentially be an option, if we find gitlab attractive from a functionality standpoint. The question I'd have about that is whether it

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/28/15 11:43 AM, Andres Freund wrote: On 2015-09-28 09:41:18 -0700, David Fetter wrote: Since you're convinced that this is an unqualified win, please put together a project plan for switching from our current system to Github. Err, no. That's a waste of all our time. It has been stated

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Tom Lane wrote: > Now, running gitlab on community-owned hardware would potentially be an > option, if we find gitlab attractive from a functionality standpoint. > The question I'd have about that is whether it has a real development > community, or is open-source in name only. If github did go

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/28/2015 03:40 PM, Alvaro Herrera wrote: > Tom Lane wrote: > >> Now, running gitlab on community-owned hardware would potentially be an >> option, if we find gitlab attractive from a functionality standpoint. >> The question I'd have about that is whether it has a real development >>

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/28/2015 04:08 PM, Gavin Flower wrote: JD Linux kernel project uses bugzilla (https://bugzilla.kernel.org) and so does LibreOffice (https://bugs.documentfoundation.org) I think they are both fairly big projects in for the long haul. I am not anti-bugzilla, just not all that familiar

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Ryan Pedela (rped...@datalanche.com) wrote: > I haven't used Gitlab extensively, but it has a feature set similar to > Github and then some [1]. The OSS project does seem active [2], but it is > still relatively new. I've set it up and used it for a relatively small environment and was *not*

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Tom Lane (t...@sss.pgh.pa.us) wrote: > Josh Berkus writes: > > The infra team seems to be good with debbugs, and several committers > > seem to like it, why not go with it? > > It certainly seems like debbugs is the proposal to beat at this point. Agreed. > In the end

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

JD, * Joshua D. Drake (j...@commandprompt.com) wrote: > On 09/28/2015 03:40 PM, Alvaro Herrera wrote: > >We already made a similar choice some years ago when we started > >depending on the then-recently open sourced SourceForge code for > >pgFoundry. That didn't turn out all that well in the

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Thursday 24 September 2015 12:10:07 Ryan Pedela wrote: > Kam Lasater wrote: > > 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. > > Why not just use Github

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/28/15 9:03 PM, Stephen Frost wrote: * Ryan Pedela (rped...@datalanche.com) wrote: I haven't used Gitlab extensively, but it has a feature set similar to Github and then some [1]. The OSS project does seem active [2], but it is still relatively new. I've set it up and used it for a

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Jim Nasby (jim.na...@bluetreble.com) wrote: > 2 years ago is when they first released the enterprise edition, > which according to [1] had "The most important new feature is that > you can now add members to groups of projects." It needed a lot more than a single feature. > So looking at it

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/28/2015 07:18 PM, Stephen Frost wrote: JD, debbugs is being used by Debian, and has been since before our first release (I believe- according to wikipedia, it started in 1994..). Further, it's now being used by the GNU project for things as important (well, to some ;) as Emacs. I

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Hello, I accidently sent this directly to TGL so here we go: Hello, I am pretty sure RT can do what I am about to suggest but I know Redmine can do it. Consider the following situation: Robert Haas posts: Parallelized Joins patch New issue is created (via email) Patch is

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 24 September 2015 at 12:16, Tom Lane wrote: > I promised myself I'd stay out of this discussion, but ... > > Josh Berkus writes: > > I know we're big on reinventing the wheel here, but it would really be a > > better idea to use an established product

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/25/2015 09:55 AM, Joe Conway wrote: On 09/25/2015 09:32 AM, Tom Lane wrote: 2. There's no visibility for outsiders as to what issues are open or recently fixed. Not being outsiders, I'm not sure that we are terribly well qualified to describe this problem precisely or identify a good

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/25/2015 09:32 AM, Tom Lane wrote: > 2. There's no visibility for outsiders as to what issues are open or > recently fixed. Not being outsiders, I'm not sure that we are terribly > well qualified to describe this problem precisely or identify a good > solution --- but I grant that there's a

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/25/2015 10:27 AM, Simon Riggs wrote: 2. There's no visibility for outsiders as to what issues are open or recently fixed. Not being outsiders, I'm not sure that we are terribly well qualified to describe this problem precisely or identify a good solution --- but I grant

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Fri, Sep 25, 2015 at 11:32 AM, Tom Lane wrote: > Simon Riggs writes: >> I have frequently been the agent of change in matters of process, but I see >> no useful change here, just lots of wasted time. But then why are we even >> talking about change?

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Simon Riggs writes: > I have frequently been the agent of change in matters of process, but I see > no useful change here, just lots of wasted time. But then why are we even > talking about change? What thing is broken that needs to be fixed? Why is > adopting a new package

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Joe Conway writes: > On 09/25/2015 09:32 AM, Tom Lane wrote: >> I do not know how much emphasis the project should place on point #2. >> By definition, fixing that will not return any direct benefit to us. > I would argue that there is some benefit for us in terms of

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 25 September 2015 at 11:55, Joe Conway wrote: > On 09/25/2015 09:32 AM, Tom Lane wrote: > > 2. There's no visibility for outsiders as to what issues are open or > > recently fixed. Not being outsiders, I'm not sure that we are terribly > > well qualified to describe this

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 25 September 2015 at 11:32, Tom Lane wrote: > Simon Riggs writes: > > I have frequently been the agent of change in matters of process, but I > see > > no useful change here, just lots of wasted time. But then why are we even > > talking about

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 2:14 PM, Alvaro Herrera wrote: > Jeff Janes wrote: > > > > I'd rather, say, put some more work into cleaning the kruft out of the > > To-Do list, then put that effort into migrating the kruft to a fancier > > filing cabinet. > > Casual users

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/25/2015 10:11 AM, Simon Riggs wrote: > > I do not know how much emphasis the project should place on point #2. > By definition, fixing that will not return any direct benefit to us. I would argue that there is some benefit for us in terms of advocacy. There are also some

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/25/2015 10:27 AM, Simon Riggs wrote: > On 25 September 2015 at 11:32, Tom Lane 1. We don't have a good process for making sure things don't "slip > through > the cracks". I think everyone more or less relies on Bruce to run > through > his mailbox

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

2015-09-25 9:57 GMT+02:00 Torsten Zuehlsdorff : > > > On 24.09.2015 20:23, David Fetter wrote: >> >> On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: >>> >>> Kam Lasater wrote: I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably in

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 25.09.2015 10:04, Albert Cervera i Areny wrote: 2015-09-25 9:57 GMT+02:00 Torsten Zuehlsdorff : On 24.09.2015 20:23, David Fetter wrote: On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: Kam Lasater wrote: I'd suggest: Github Issues, Pivotal

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 24.09.2015 20:23, David Fetter wrote: On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: Kam Lasater wrote: 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Fri, Sep 25, 2015 at 12:40 AM, Tom Lane wrote: > Josh Berkus writes: > > On 09/24/2015 12:55 PM, Tom Lane wrote: > >> I agree with the idea that we don't yet want to give the impression that > >> this is the official bug tracker. However, "beta-bugs"

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: > Josh Berkus wrote: > > When we discussed this 8 years ago, Debian said debbugs wasn't ready for > > anyone else to use. Has that changed? > > Emacs uses debbugs now, so there's at least one non-Debian user. Oh? Nice. debbugs matches up

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Thomas Kellerer (spam_ea...@gmx.net) wrote: > > And email integration for Jira is nonexistant. > > That is not true. We do have an email integration where customers can create > issues by sending an email to a specific "Jira Email" address. And as far as > I know this is a standard module from

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

> And email integration for Jira is nonexistant. That is not true. We do have an email integration where customers can create issues by sending an email to a specific "Jira Email" address. And as far as I know this is a standard module from Atlassian. I _think_ it can also be configured that you

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 23.09.2015 20:43, Robert Haas wrote: On Wed, Sep 23, 2015 at 2:30 PM, Kam Lasater wrote: 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. I venture to say that we are

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 24.09.2015 01:33, Josh Berkus wrote: On 09/23/2015 03:05 PM, Jim Nasby wrote: On 9/23/15 3:12 PM, Thomas Kellerer wrote: They also support Postgres as their backend (and you do find hints here and there that it is the recommended open source DBMS for them - but they don't explicitly state

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Thu, Sep 24, 2015 at 1:25 AM, Thomas Munro wrote: > The two most common interactions could go something like this: > > 1. User enters bug report via form, creating an issue in NEW state > and creating a pgsql-bugs thread. Someone responds by email that this >

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/24/2015 10:28 AM, k...@rice.edu wrote: On Wed, Sep 23, 2015 at 04:33:33PM -0700, Josh Berkus wrote: On 09/23/2015 03:05 PM, Jim Nasby wrote: On 9/23/15 3:12 PM, Thomas Kellerer wrote: They also support Postgres as their backend (and you do find hints here and there that it is the

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 04:33:33PM -0700, Josh Berkus wrote: > On 09/23/2015 03:05 PM, Jim Nasby wrote: > > On 9/23/15 3:12 PM, Thomas Kellerer wrote: > >> They also support Postgres as their backend (and you do find hints > >> here and > >> there > >> that it is the recommended open source DBMS

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

All, * Stephen Frost (sfr...@snowman.net) wrote: > Not saying it's perfect, of course, but it's probably the best option > for minimizing impact on our existing process. I discussed the current state of debbugs with Don Armstrong (one of the main individuals behind it) and his opinion is that

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/24/2015 10:24 AM, Stephen Frost wrote: > * Joe Conway (m...@joeconway.com) wrote: >> On 09/24/2015 10:08 AM, Stephen Frost wrote: >>> debbugs does most of the above by default, no programming needed... I'm >>> sure we could get it to integrate with the commitfest and have a git >>> commit

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Kam Lasater wrote: > 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. Why not just use Github issues? 1. You can set it up to send emails to the list when an issue

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Tom Lane (t...@sss.pgh.pa.us) wrote: > Stephen Frost writes: > > Are there any objections to pginfra standing up bugs.postgresql.org with > > debbugs? Obviously, it'd be more-or-less beta as we play with it, and > > we could set it up as beta-bugs.p.o, if there's concern

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Joe Conway (m...@joeconway.com) wrote: > On 09/24/2015 10:08 AM, Stephen Frost wrote: > > debbugs does most of the above by default, no programming needed... I'm > > sure we could get it to integrate with the commitfest and have a git > > commit hook which sends the appropriate email to it

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Stephen Frost writes: > Are there any objections to pginfra standing up bugs.postgresql.org with > debbugs? Obviously, it'd be more-or-less beta as we play with it, and > we could set it up as beta-bugs.p.o, if there's concern about that. I agree with the idea that we don't

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Thu, Sep 24, 2015 at 6:16 PM, Tom Lane wrote: > Yeah; "let's write our own bug tracker" is a good way to make sure nothing > comes of this. On the other hand, "let's get all the Postgres hackers to > change their habits" is an equally good way to make sure nothing comes of

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/24/2015 07:03 PM, Josh Berkus wrote: > On 09/23/2015 10:25 PM, Thomas Munro wrote: >> On Thu, Sep 24, 2015 at 1:31 PM, Joe Conway wrote: >>> On 09/23/2015 05:21 PM, Thomas Munro wrote: Do you think it would make any sense to consider evolving what we have

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/24/2015 12:55 PM, Tom Lane wrote: > Stephen Frost writes: >> Are there any objections to pginfra standing up bugs.postgresql.org with >> debbugs? Obviously, it'd be more-or-less beta as we play with it, and >> we could set it up as beta-bugs.p.o, if there's concern

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/23/2015 10:25 PM, Thomas Munro wrote: > On Thu, Sep 24, 2015 at 1:31 PM, Joe Conway wrote: >> On 09/23/2015 05:21 PM, Thomas Munro wrote: >>> Do you think it would make any sense to consider evolving what we have >>> already? At the moment, we have a bug form, and when

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Josh Berkus (j...@agliodbs.com) wrote: > I know we're big on reinventing the wheel here, but it would really be a > better idea to use an established product than starting over from > scratch. Writing a bug tracker is a lot of work and maintenance. I tend to agree. > > The two most common

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/24/2015 10:08 AM, Stephen Frost wrote: > debbugs does most of the above by default, no programming needed... I'm > sure we could get it to integrate with the commitfest and have a git > commit hook which sends the appropriate email to it also. > > That the emacs folks are using it makes me

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

I promised myself I'd stay out of this discussion, but ... Josh Berkus writes: > I know we're big on reinventing the wheel here, but it would really be a > better idea to use an established product than starting over from > scratch. Writing a bug tracker is a lot of work and

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: > Kam Lasater wrote: > > 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. > > Why not just use

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Josh Berkus writes: > On 09/24/2015 12:55 PM, Tom Lane wrote: >> I agree with the idea that we don't yet want to give the impression that >> this is the official bug tracker. However, "beta-bugs" could give the >> impression that it was specifically for bugs about 9.5beta,

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Kam Lasater wrote: > 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: > Kam Lasater wrote: > > > 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/23/2015 11:33 AM, Stephen Frost wrote: * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote: Kam Lasater wrote: 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.

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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/23/2015 11:23 AM, Alvaro Herrera wrote: Kam Lasater wrote: 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,

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Jeff Janes wrote: > For whatever it is worth, one of the frustrations I've had with projects > (other than PostgreSQL) of which I am a casual users is that reporting a > single bug meant signing up for yet another account on yet another site and > learning yet another bug tracking system. Right.

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 5:00 PM, Stephen Frost wrote: > Kam, > > * Kam Lasater (c...@seekayel.com) wrote: > > > ... The above-referenced individuals > > > would be the bug tracking system curators, of course. Unless it's got > > > serious technical issues, the infrastructure

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/23/15 3:12 PM, Thomas Kellerer wrote: They also support Postgres as their backend (and you do find hints here and there that it is the recommended open source DBMS for them - but they don't explicitly state it like that). We are using Jira at the company I work for and all Jira

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

>> Personally I'd also change sending patches in emails to github pull >> requests :). > > That won't happen, at least not this decade. FWIW, a year ago I might have agreed that a github pull-request would be preferable. However, since, I have grown to really like the patch via email approach.

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 9/23/15 3:29 PM, Alvaro Herrera wrote: Joshua D. Drake wrote: Until that happens asking anyone to put resources into this idea is just not worth it. I wonder if you still have this conversation archived: Date: Thu, 10 May 2007 11:30:55 -0400 From: Andrew Dunstan To:

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 2:30 PM, Kam Lasater wrote: > 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. I venture to say that we are succeeding as it is, although of course we

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Szymon Lipiński wrote: > Then I need to read through the emails. This is not user friendly too, as I > need to click through the email tree, and if an email has multiple replies, > it is usually hard not to omit some of them, as after going into a reply, I > need to click to get to the parent

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 5:10 PM, Szymon Lipiński wrote: > > > On 23 September 2015 at 22:07, Stephen Frost wrote: > >> * Josh Berkus (j...@agliodbs.com) wrote: >> > On 09/23/2015 11:18 AM, Kam Lasater wrote: >> > > At this point not having one is

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Szymon, * Szymon Lipiński (mabew...@gmail.com) wrote: > a couple of days ago I was reading through the tickets in the Django bug > tracker. It was much easier to find any information about the things to > work on than currently for Postgres. I tend to doubt that a bug tracker would change that

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. There are several OSS

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/23/2015 11:43 AM, Robert Haas wrote: > If somebody does do the work, then we get to the next question: if we > had an accurate list of open bugs, would anybody who currently doesn't > work on fixing those bugs step up to help fix them? I hope so, but I > don't know. If not, we might not

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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 23 September 2015 at 22:07, Stephen Frost wrote: > * Josh Berkus (j...@agliodbs.com) wrote: > > On 09/23/2015 11:18 AM, Kam Lasater wrote: > > > At this point not having one is borderline negligent. I'd suggest: > > > Github Issues, Pivotal Tracker or Redmine (probably in

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 09/23/2015 11:18 AM, Kam Lasater wrote: > > 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. First,

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Kam, * Kam Lasater (c...@seekayel.com) wrote: > > ... 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

* Josh Berkus (j...@agliodbs.com) wrote: > On 09/23/2015 11:18 AM, Kam Lasater wrote: > > 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

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Joshua D. Drake wrote: > Until that happens asking anyone to put resources into this idea is just not > worth it. I wonder if you still have this conversation archived: Date: Thu, 10 May 2007 11:30:55 -0400 From: Andrew Dunstan To: "Joshua D. Drake", Magnus Hagander,

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On Wed, Sep 23, 2015 at 11:43 AM, Robert Haas wrote: > On Wed, Sep 23, 2015 at 2:30 PM, Kam Lasater wrote: > > Thanks for the suggestion. However, an issue tracker is not a > > replacement for mailing list(s) and vice versa. They are both > > necessary

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Josh Berkus wrote: > When we discussed this 8 years ago, Debian said debbugs wasn't ready for > anyone else to use. Has that changed? Emacs uses debbugs now, so there's at least one non-Debian user. -- Álvaro Herrerahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7

<    1   2   3   >