First off, it looks fantastic. With CP slowly dying I think it's worth publicizing this for any other projects looking at migrating. I plan on doing a big blog post after the migration is complete anyway, but this probably deserves its own, if you want to write it.
Couple of minor things: * I don't think the "unassigned" tag is useful * Is there value in keeping low/medium around? High I can see being useful (and ideally all "high" issues are in the next milestone, and a release doesn't go out until all high issues are either fixed or downgraded) but I'm not sure there's much distinction between low, medium, and none. Once those are sorted I think we're good to go. Be sure to use the ironpythonbot account to do the actual import; I have the credentials if you need them. - Jeff On Mon, Dec 8, 2014 at 7:03 PM, Slide <slide.o....@gmail.com> wrote: > The issues have been imported to https://github.com/slide/ipimport8/issues > . > > These issues are the ones that have more than 1 vote or have been updated > since Mar 25, 2013 (I don't know why I picked that date). It is only issues > that are not Resolved or Closed in CodeProject. > > I removed the milestone stuff. > > Let me know what you think. > > > On Mon Dec 08 2014 at 5:14:08 AM Jeff Hardy <jdha...@gmail.com> wrote: > >> Release it not even remotely consistent in CodePlex so I'd rather start >> from scratch on milestones. You could just drop it completely, I don't >> think we'd lose anything. >> >> Will you be able to do one final test run? What's there looks good but >> I'd liek to see it one more time before committing. :) >> >> Once it's ready I'll close all of the issues on CP and put up a marker >> issue directing people to GitHub. >> >> - Jeff >> >> On Mon, Dec 8, 2014 at 11:38 AM, Slide <slide.o....@gmail.com> wrote: >> >>> I don't have an opinion either way. The code is easy to change, so if >>> there are strong opinions one way or another, just let me know which way we >>> want to go. >>> >>> >>> On Mon Dec 08 2014 at 1:19:20 AM Pawel Jasinski < >>> pawel.jasin...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I have a question/suggestion. I was under impression, the milestone >>>> should be interpreted as "planned to be fixed in a release". The test >>>> run converts whatever is in "Release" in codeplex into milestone, >>>> which is technically correct. However the "Release" in codeplex >>>> appears to be abused or not maintained and is more aligned with "bug >>>> in version". Would it make more sense to not set any milestone and >>>> use value as a label instead? >>>> >>>> >>>> >>>> Cheers >>>> --pawel >>>> >>>> >>>> On Mon, Dec 8, 2014 at 4:51 AM, Slide <slide.o....@gmail.com> wrote: >>>> > This is the most recent run from a couple months ago or so. >>>> > https://github.com/slide/ipimport7/issues >>>> > >>>> > >>>> > On Sun, Dec 7, 2014, 13:10 Jeff Hardy <jdha...@gmail.com> wrote: >>>> >> >>>> >> On Sun, Dec 7, 2014 at 10:37 AM, Pawel Jasinski < >>>> pawel.jasin...@gmail.com> >>>> >> wrote: >>>> >>> >>>> >>> hi, >>>> >>> >>>> >>> when will the conversion of issues from codeplex to github take >>>> place? >>>> >>> >>>> >>> Or simpler, where should I add new issues now? >>>> >> >>>> >> >>>> >> Soon-ish, I think. Alex, did you have a demo from a recent run? >>>> >> >>>> >> My thought right now is to put the existing ones into the "main" >>>> repo and >>>> >> only put 3.0-specific items in ironpython3. >>>> >> >>>> >> Any new ones should be put into the GitHub "main" repo. >>>> >> >>>> >> - Jeff >>>> _______________________________________________ >>>> Ironpython-users mailing list >>>> Ironpython-users@python.org >>>> https://mail.python.org/mailman/listinfo/ironpython-users >>>> >>> >>> _______________________________________________ >>> Ironpython-users mailing list >>> Ironpython-users@python.org >>> https://mail.python.org/mailman/listinfo/ironpython-users >>> >>> >>
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
