Re: [erlang-questions] [ANN] Announcing Erlang Issue Tracker bugs.erlang.org
Jesper Louis Andersen <[email protected]> Wed, 21 Oct 2015 21:29:55 +0200
| Newsgroups | gmane.comp.lang.erlang.bugs,gmane.comp.lang.erlang.general |
|---|---|
| Message-ID | <CAGrdgiVwM1MWgxzVRtxDggDvQ6gYn3dFc8+m922VdovmYhgMQw@mail.gmail.com> |
On Wed, Oct 21, 2015 at 9:00 PM, Kostis Sagonas <[email protected]> wrote: > Why re-invent the wheel (and complicate our lives)? On the Jira/Bugzilla scale, Github Issues tracks in at about 1 nano-Jira. That is, Jira can do some things in the enterprise setting which you can't easily get with Github. It is nice for small simple projects, but there are many large projects which run their "own" Jira-instances for the reason of interoperating. If I remember correctly, Jira can link to other internal Jira's at Ericsson, which is necessary to be able to track issues cross-projects, some of which are obviously internal and closed source. Given such constraints, running your own instance on the "outside of the firewall/walled garden" is the right choice. -- J. _______________________________________________ erlang-bugs mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-bugs