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 there, I'm sure one of them would also work.
> > 
> > Why not just use Github issues?
> I will also vote for github.  We have github mirror now. 
> In a pinch, you can use gitlab.

Github is a company, and companies go out of business all the time,
frequently without warning.  However healthy it may look right now,
this is a scenario for which we need to have plans.

What is your plan for this contingency?

I assure you that when it's happening, the very last thing on the mind
of the people winding down the company is whether some project's bug
tracker gets properly exported and its functionality ported to another
compatible system.

> PS mail lists outdated IMHO.

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.

There are a good many decisions I would make differently if I were
waving a magic wand over a green field project.  Neither magic wands
nor a green field project are in operation here.

David Fetter <da...@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fet...@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to