git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Mar 1, 2012, 05:40 UTC
Message-ID
<CAH5451m-Ks+UywfMWfC1TS=5n102VasdgJ0tg-pGym69B2NPQQ@mail.gmail.com>
In-Reply-To
<buo399s3nph.fsf@dhlpc061.dev.necel.com>
On 1 March 2012 16:16, Miles Bader <miles@gnu.org> wrote:
Show 9 quoted lines
> Andrew Ardill <andrew.ardill@gmail.com> writes:
>> Additionally, if we are not prepared to use non-Free tools, we should
>> probably stop using github.
>
> I think the issue isn't "using" non-free tools so much as it's getting
> _locked into_ non-free tools.
>
> So if JIRA makes all its data trivially exportable in a format which
> is easy to use,
JIRA provides the ability to trivially export any 'filter' as XML or
CSV data files. A filter is simply a search, and can contain every
single issue in the database. Some pieces of information are slightly
more difficult to migrate.
- Issue attachments such as screenshots are not stored in the
database, and we would have to request them in order to retrieve them.
- User information and configuration data is only available in a full
site backup (which is available on request).
- CSV export option does not include comments. (XML, and Word formats do)

Additionally, there are quite a number of tools to allow migration between JIRA and other tools, and in my experience Atlassian are quite helpful when you try and move off their products.

> and there's some way of isolating references to it so
> that it's possible to switch to something else without undue hardship

JIRA has the capacity to automatically link issues to commits which mention issue numbers, however this is by no means essential or necessary functionality. JIRA will be happy completely detached from the rest of the world, and will provide additional functionality gradually as it becomes more integrated. Some functionality it can provide without forming hard links with the outside world (like polling the repository and providing continuous builds)

The primary thing to look out for would be other sites linking to the issue tracker. Unfortunately, there is no way at the moment to provide an alternate URI for the tracker, so it is hard to avoid this from happening.

Regards,
Andrew Ardill
Previous: Miles BaderNext: Scott Chacon
Message 13 of 37 in “Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests”
  1. opticyclicFeb 29, 2012
  2. Brian GernhardtFeb 29, 2012
  3. Junio C HamanoFeb 29, 2012
  4. Jonathan NiederFeb 29, 2012
  5. Andrew ArdillFeb 29, 2012
  6. Greg TroxelMar 1, 2012
  7. Andrew ArdillMar 1, 2012
  8. Junio C HamanoMar 1, 2012
  9. Andrew ArdillMar 1, 2012
  10. Junio C HamanoMar 1, 2012
  11. Andrew ArdillMar 1, 2012
  12. Miles BaderMar 1, 2012
  13. Andrew ArdillMar 1, 2012
  14. Scott ChaconMar 1, 2012
  15. Junio C HamanoMar 1, 2012
  16. Thomas RastMar 1, 2012
  17. Ævar Arnfjörð BjarmasonMar 1, 2012
  18. Andrew ArdillMar 1, 2012
  19. Andrew ArdillMar 1, 2012
  20. Junio C HamanoMar 1, 2012
  21. Neal KreitzingerMar 2, 2012
  22. Jonathan NiederMar 2, 2012
  23. Junio C HamanoMar 2, 2012
  24. Neal KreitzingerMar 2, 2012
  25. Jonathan NiederMar 2, 2012
  26. Junio C HamanoMar 2, 2012
  27. Andreas EricssonMar 2, 2012
  28. Junio C HamanoMar 2, 2012
  29. Andrew ArdillMar 7, 2012
  30. Vincent van RavesteijnMar 7, 2012
  31. Joern HuxhornMar 7, 2012
  32. Jonathan NiederMar 7, 2012
  33. Joern HuxhornMar 7, 2012
  34. Pau Garcia i QuilesMar 7, 2012
  35. Phil HordMar 7, 2012
  36. Carlos Martín NietoFeb 29, 2012
  37. Sitaram ChamartyFeb 29, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.