Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Ryan Pedela
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id CACu89FS5fNXCjwVVWCOFa2pn_34iUnmaFExpbtUqjVKXgpbKxQ@mail.gmail.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Josh Berkus <josh@agliodbs.com>)
Responses Re: No Issue Tracker - Say it Ain't So!  (David Fetter <david@fetter.org>)
Re: No Issue Tracker - Say it Ain't So!  (YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>)
List pgsql-hackers
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 is created or updated.
2. Replies to the email will automatically update the issue on Github.
3. Github is where most of the OSS activity happens now.
4. If Github goes away, so what? The core workflow never changes.

Thanks,
Ryan Pedela

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: clearing opfuncid vs. parallel query
Next
From: Greg Stark
Date:
Subject: Re: No Issue Tracker - Say it Ain't So!