Phil Holmes wrote Monday, May 04, 2015 3:57 PM
> As promised, a starter list of requirements for the issue handling system, > to allow us to check potential replacements to Google code. > > 14. Allow export of the issue database in CSV form Actually GoogleCode (and Allura for that matter) export the text part of the DB as a JSON file, with urls pointing to the attachments so these can be located and exported by a script at a later time. The GoogleCode CSV export just exports the index (ie no text) which is singularly useless for backup and transfer. So this requirement might be better written as: 14. Allow export of the issue database as a zipped JSON file containing all the index variables and discussion text, together with a means of accessing all attachments so these may be re-associated correctly with the relevant text. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
