[Ironpython-users] converting issues from codeplex to github

[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 <pawel.jasinski at 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.mix at 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 <jdhardy at gmail.com> wrote:
> >>
> >> On Sun, Dec 7, 2014 at 10:37 AM, Pawel Jasinski <
> pawel.jasinski at 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 at python.org
> https://mail.python.org/mailman/listinfo/ironpython-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20141208/d3bc0e5a/attachment.html>