I started a test run of importing the Avogadro SourceForge bugs and feature requests to GitHub issues: https://github.com/ghutchis/sfimporttest/issues
* It's very difficult to script importing the milestone versions - but it should be easy to make some batch changes (e.g., find the v_1_0 label and assign a 1.0 milestone) * I think the "auto-migrated" and "source forge" labels are redundant. Which one should I kill? (I'd keep the "auto-migrated" and kill the "source forge" tag) I'll wait to hear some feedback and then start a batch run on Tuesday, Apr. 26th. After the import of issues is done, I'm going to turn off the SF trackers and have them point at the GitHub page. -Geoff ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Avogadro-devel mailing list Avogadro-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avogadro-devel
