Richard Hipp wrote:
> Is there a better story for moving between any two bug tracking
> systems? Do there exist any two bug tracking systems in the world were
> you can move from one to the other without having to write some scripts to
> transform the data?
I can't tell whether you're asking rhetorically or in earnest. I
think rhetorically.
To which I reply that I make no claim that I am being fair. :-)
I just want to use fossil, and am looking for talking points to
convince others that the two points I initially enumerated are not
going to bite us.
> Fossil can give you the ticket data as SQL. I think that is probably
> about as portable as ticket data is going to get.
... says the top SQL expert between here and the Romulan Neutral Zone. :-)
>From an information theoretic perspective, yes, all the data is
available. But that doesn't necessarily mean that it's easy for a poor
user, unfamiliar with both the Fossil database schema and the import
requirements of the target tool, to move the data between them.
> You can use the "fossil sql" command to run ".dump" to get the ticket
> content and then load that content into *any* SQL database (MySQL,
> PostgreSQL, Oracle, SQL Server - name your poison) You will then have
> to transform the schema into whatever your target system expects. But I
> think that is always going to be the case, no?
I hope not. Microsoft Office products can import/export to/from
different formats. Lots of products "know" about the particular file
formats required by other specific products for the purposes of export.
Fossil *could* support export to JIRA+git in particular, for example, by
providing a tool that (a) exports to JIRA's supported JSON import format,
(b) collects the mapping from the fossil ticket IDs to the JIRA ticket
IDs, then (c) does a git export but massages the check-in comments
according to the data collected in (b).
Such a tool that is written and tested by the fossil devs would
obviously be preferable to whatever my sad little user-brain could
generate.
I make no claim that writing such a thing would be the best use of the
fossil devs' time -- again, just wondering what is out there.
> We do low-ceremony code review on SQLite.
{snip}
> We use more ceremony for testing.
{snip}
Thanks for sharing that, Richard.
--
Eric A. Rubin-Smith
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
