Monday, October 20, 2014

dygraphs issues on GitHub

I've moved the dygraphs issue tracker from Google Code over to GitHub issues. The new issues link back to the old, though not vice versa.

My hope is that moving to GitHub will increase community involvement, since it's a more familiar, modern system.

The migration process was fairly painless. I used a tweaked version of the google-code-issues-migrator and took inspiration from beet's moving from Google Code to GitHub: a horrible, ultimately rewarding odyssey.

1 comment:

  1. Congratulations on dygraphs - I hope to deploy it sometime soon.

    Just a suggestion - set up a proper 301 redirect on the old link, as it now gives a 404.