We need to do something with the #__tracker_projects table first as that has GitHub bot credentials in it. Otherwise there's no issue with that at all IMO. It'll be even better if we can take joomla/joomla-cms#10991 when it's tested out and merge it to the Framework library then we can just use native Joomla API to do it.

Aside from that, a cron scripting a mysqldump run is more than enough.

True haven't thought of those credentials... There is a --ignore-table option in mysqldump ?

joomla/joomla-cms#10991 looks interesting, I remember I did one attempt years ago, maybe mine was not good enough - I'd say let's use mysqldump until the PR is merged...

btw, I was just playing with labels and milestones... no need to hurry ?

Sanitized file's at https://issues.joomla.org/uploads/issuesj_tracker_2016-07-16.txt (rename to .sql and you're good to go). Just note it's a large file, start the download and take a drink break.

Zip it up and it will be TINY

https://issues.joomla.org/uploads/db.zip but it's still larger than the CMS download.

Both are 404ing :(

Whoops. My FTP client was still pointing to the old server, the ZIP file's uploaded to the new one and the TXT is uploading now.

looks good, THANKS!
I hope it will be updated from time to time...