Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Slide
I'll have to figure out where the "unassigned" tag is coming from, its just part of the meta data in some of the fields, so I'll look at filtering it out. Filtering out anything but "high" for severity should be pretty easy. Do you want to see a full import again with those items? On Mon Dec 08 2

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Jeff Hardy
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'

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Slide
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

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Jeff Hardy
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. :) On

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Slide
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 wrote: > Hi, > > I have a question/suggestion. I was under impression, the milestone > sho

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-08 Thread Pawel Jasinski
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 no

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-07 Thread Slide
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 wrote: > On Sun, Dec 7, 2014 at 10:37 AM, Pawel Jasinski > wrote: > >> hi, >> >> when will the conversion of issues from codeplex to github take place? >>

Re: [Ironpython-users] converting issues from codeplex to github

2014-12-07 Thread Jeff Hardy
On Sun, Dec 7, 2014 at 10:37 AM, Pawel Jasinski 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 existin