FYI, this is an example of what my tool does for the issues from CodePlex
https://github.com/slide/ip-test2/issues
I haven't implemented the vote or date filtering yet, and this is not all
of the issues from CodePlex, just some of them.
On Fri, Mar 21, 2014 at 6:33 AM, Slide wrote:
> I think
On Fri, Mar 21, 2014 at 4:57 PM, Slide wrote:
> This is in the post 2.7.5 timeframe, correct? We don't want to do this
> before that is released?
>
Yeah. Plus hopefully a bunch of them will get fixed and then it's not a
concern. :)
- Jeff
>
>
> On Fri, Mar 21, 2014 at 9:37 AM, Jeff Hardy wro
IMO it is fine to lose them. I think codeplex automatically notifies you if an
issue you opened has been closed (even if it is years later), so perhaps just
going through and closing all of the < 2 vote or old issues with a notice that
says "open a new issue on github if this is still relevant"
This is in the post 2.7.5 timeframe, correct? We don't want to do this
before that is released?
On Fri, Mar 21, 2014 at 9:37 AM, Jeff Hardy wrote:
> On Fri, Mar 21, 2014 at 4:28 PM, Slide wrote:
>
>> I could write a tool to do that too...screen scraping is actually kind of
>> fun.
>>
>
> I wou
On Fri, Mar 21, 2014 at 4:28 PM, Slide wrote:
> I could write a tool to do that too...screen scraping is actually kind of
> fun.
>
I would say you're a sick, twisted individual, but I get unreasonable joy
out of forcing cmd.exe and MSBuild to do what I want, so I'll remain
silent. :)
> My init
I could write a tool to do that too...screen scraping is actually kind of
fun. My initial plan was just to implement vote and date filters in my
current tool that ports issues over, but closing things is fine with me too.
On Fri, Mar 21, 2014 at 9:14 AM, Keith Rome wrote:
> IMO it is fine to
On Fri, Mar 21, 2014 at 1:33 PM, Slide wrote:
> I think if you do > 1 vote, you'll miss a lot of issues that are valid, but
> it would provide for a cleaner slate to begin with on GitHub. There are a
> LOT of issues on CodePlex that are leftover from the MS days (internal bug
> tracker migration)
I think if you do > 1 vote, you'll miss a lot of issues that are valid, but
it would provide for a cleaner slate to begin with on GitHub. There are a
LOT of issues on CodePlex that are leftover from the MS days (internal bug
tracker migration) that would be really nice to get rid of since we don't
On Fri, Mar 21, 2014 at 1:20 PM, Slide wrote:
>> Either way, the primary issue list will move to GitHub. The question is
>> how:
>>
>> 1) Clean issue list in GH, abandon all CodePlex issues
>> 2) Copy all open issues from CP
>> 3) Copy all open issues from past 12 months
>> 4) Copy all open issues
>
> Either way, the primary issue list will move to GitHub. The question is
> how:
>
> 1) Clean issue list in GH, abandon all CodePlex issues
> 2) Copy all open issues from CP
> 3) Copy all open issues from past 12 months
> 4) Copy all open issues with > 1 votes
>
>
Do you mean issues OPENED within
On Fri, Mar 21, 2014 at 9:58 AM, Pawel Jasinski
wrote:
> Hi,
>
> sometimes ago there was a plan to migrate from codeplex to github
> issue tracking.
> Since we are talking about a workflow, would it make sense to do migration
> now?
Not *right now*, but after 2.7.5 is out, just to cut down on th
On Fri, Mar 21, 2014 at 8:08 AM, Vernon D. Cole wrote:
> Thank you, Jeff!!
>
> This is wonderful! I have already cloned the new repo on my Windows
> development machine (such as it is, and old Windows 7 laptop) and will put
> it on my Ubuntu development machine (the one I work on daily) in a few
Hi,
sometimes ago there was a plan to migrate from codeplex to github
issue tracking.
Since we are talking about a workflow, would it make sense to do migration now?
--pawel
___
Ironpython-users mailing list
Ironpython-users@python.org
https://mail.pyth
Thank you, Jeff!!
This is wonderful! I have already cloned the new repo on my Windows
development machine (such as it is, and old Windows 7 laptop) and will put
it on my Ubuntu development machine (the one I work on daily) in a few
minutes.
Two questions remain that were not answered in the Read
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] PEP 397 -- Python launcher for Windows
--
ISSUES
1. [New issue] PEP 397 -- Python launcher for Windows
http://ironpython.codeplex
15 matches
Mail list logo
