Here's the actual import with that filter:
[5] - https://github.com/slide/ipimport5/issues
On Tue, Mar 25, 2014 at 8:07 AM, Slide wrote:
> Ok, I didn't do the actual import, but there are 236 issues that would be
> migrated.
>
>
> On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
>
>> On Tue
Ok, I didn't do the actual import, but there are 236 issues that would be
migrated.
On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> > Here are four repos that show the different options
> >
> > [1] - Open issues from CodePlex only - 1007 iss
On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> Here are four repos that show the different options
>
> [1] - Open issues from CodePlex only - 1007 issues migrated
> [2] - Open issues filtered by votes >= 1 - 763 issues migrated
> [3] - Open issues filtered by created/updated since 25/03/2013 - 11
hmmm, I didn't write my filtering that way, but I can probably add it...
On Tue, Mar 25, 2014 at 6:53 AM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 1:28 PM, Slide wrote:
> > Here are four repos that show the different options
> >
> > [1] - Open issues from CodePlex only - 1007 issues migrate
Here are four repos that show the different options
[1] - Open issues from CodePlex only - 1007 issues migrated
[2] - Open issues filtered by votes >= 1 - 763 issues migrated
[3] - Open issues filtered by created/updated since 25/03/2013 - 111 issues
migrated
[4] - Open issues filtered by votes >=
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
t" would be enough to catch the things that fall through the cracks.
>>>>
>>>>
>>>> *Keith Rome*
>>>>
>>>> *Principal Architect @ Wintellect (www.wintellect.com
>>>> <http://www.wintellect.com>)*
>>>&g
[email protected]<mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Ironpython-users] CodePlex Issues (Was: IronPython 3 Update)
On Fri, Mar 21, 2014 at 1:33 PM, Slide
mailto:[email protected]>> wrote:
I think if you do > 1 vote, you'l
>>>
>>>
>>>
>>>
>>> Register today <https://www.wintellectnow.com/Account/Promo/ROME-13> for
>>> access to our high-quality on-demand training resources!
>>>
>>>
>>> From: Jeff Hardy
>>> Date: Friday, Ma
gt;> Register today <https://www.wintellectnow.com/Account/Promo/ROME-13> for
>> access to our high-quality on-demand training resources!
>>
>>
>> From: Jeff Hardy
>> Date: Friday, March 21, 2014 at 9:39 AM
>> To: Slide
>> Cc: "ironpython-u
day <https://www.wintellectnow.com/Account/Promo/ROME-13> for
> access to our high-quality on-demand training resources!
>
>
> From: Jeff Hardy
> Date: Friday, March 21, 2014 at 9:39 AM
> To: Slide
> Cc: "[email protected]"
> Subject: Re: [Ironpy
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
It would be really nice to get some help from the community in reviewing
the current set of issues that exist on Codeplex. There are LOTS of issues
that could be obsolete, duplicate, etc that would be nice if we could
determine the current status. If you have some time, please take a look at
the is
17 matches
Mail list logo
