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
