Re: [Avogadro-devel] GitHub issue import test
On Sun, Apr 24, 2016 at 10:27 AM, Geoffrey Hutchisonwrote: > 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) How many have contact details/any recent activity? So long as they have a tag we can filter on I think either one works. Tougher job is going through them and figuring out which are still relevant, and whether is is possible to follow up with the reporters at all. Thanks for working on this, what you have in the test looks good to me. Not sure how much I would worry about historical milestones but if it is easy it would be nice. Best, Marcus -- 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
Re: [Avogadro-devel] GitHub issue import test
> How many have contact details/any recent activity? So long as they > have a tag we can filter on I think either one works. Many had no contact details at all. For others, there's the challenge of mapping SF user names to GH users. Looking at other projects who have used this approach, they haven't bothered much with user mapping. > Tougher job is going through them and figuring out which are still relevant, > and > whether is is possible to follow up with the reporters at all. I will make a triage pass once I've imported them. > Not sure how much I would worry about historical milestones but if it is easy > it would be nice. It's pretty easy or I wouldn't have bothered. Similarly, it's easy to import the already-closed issues. For that reason, I figure it's easy enough to just do it. I'm not sure how many of the issues can be resolved in v1.x, but I think it's worth doing - at least to squash some of the 1.x bugs and keep the ideas for 2.x. -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
[Avogadro-devel] GitHub issue import test
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