That's weird, a bunch of comments are missing (maybe?). I don't see it
either, signed in or not. Wouldn't surprise me if CodePlex was bitrotting...
On Tue, Dec 15, 2015 at 7:58 AM, Slide wrote:
> https://ironpython.codeplex.com/workitem/32335 is the one I am trying to
> get all the info for.
>
>
https://ironpython.codeplex.com/workitem/32335 is the one I am trying to
get all the info for.
On Tue, Dec 15, 2015, 08:55 Jeff Hardy wrote:
> I can. What are you looking for?
>
> - Jeff
>
> On Mon, Dec 14, 2015 at 7:11 PM, Slide wrote:
>
>> Can anyone access the old CodePlex site? I was lookin
I can. What are you looking for?
- Jeff
On Mon, Dec 14, 2015 at 7:11 PM, Slide wrote:
> Can anyone access the old CodePlex site? I was looking for an old issue
> that wasn't migrated to GH.
>
> ___
> Ironpython-users mailing list
> Ironpython-users@py
Can anyone access the old CodePlex site? I was looking for an old issue
that wasn't migrated to GH.
___
Ironpython-users mailing list
[email protected]
https://mail.python.org/mailman/listinfo/ironpython-users
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
On Mon, Nov 26, 2012 at 1:49 PM, Jeff Hardy wrote:
> On Sun, Nov 25, 2012 at 8:14 AM, Slide wrote:
> >>
> >> * can you move all of the old metadata to the bottom of the issue,
> >> under "Original Codeplex Issue"?
> >
> >
> > I'm assuming you mean the "Item Details" stuff from the issues on
> Co
On Sun, Nov 25, 2012 at 8:14 AM, Slide wrote:
>>
>> * can you move all of the old metadata to the bottom of the issue,
>> under "Original Codeplex Issue"?
>
>
> I'm assuming you mean the "Item Details" stuff from the issues on CodePlex?
Yeah, and anything you parse out of the XML.
>> For the atta
On Sun, Nov 25, 2012 at 1:20 AM, Jeff Hardy wrote:
> Good work! For the most part, I like it. There are a couple of minor
> improvements I'd like to see:
>
> * can you parse the XML-formatted issues (e.g.
> http://ironpython.codeplex.com/workitem/23970) and get the interesting
> information (repo
Good work! For the most part, I like it. There are a couple of minor
improvements I'd like to see:
* can you parse the XML-formatted issues (e.g.
http://ironpython.codeplex.com/workitem/23970) and get the interesting
information (reporter, date, affected version) out of that?
* can you move all of
I also just realized that my import of labels (components in CodePlex
speak) and milestones (releases in CodePlex speak) is not working
correctly. I'll fix that as well.
On Sat, Nov 24, 2012 at 8:41 PM, Slide wrote:
> Take a look at https://github.com/slide/test/issues?state=open and let me
> k
Take a look at https://github.com/slide/test/issues?state=open and let me
know what you think. I know I need to reverse the order of the comments
once imported to GitHub, so don't look at that, but tell me what you think
about the data I am importing and the format as well. Attachments are kind
of
The completist in me would like to see everything moved, but I would
be quite happy with just the open issues. I'm OK with losing who it's
assign to and what the target release is, but I would hate to lose
comments or attached files. If possible I'd like to keep the user who
created/commented, but
I have seem to have access, I haven't tried pushing anything yet. I'll
take a look at the Extending section and what I can do help out there.
Thanks,
slide
On Mon, Apr 30, 2012 at 12:00 PM, Jeff Hardy wrote:
> On Mon, Apr 30, 2012 at 9:05 AM, Slide wrote:
>> This sounds like a great idea Jeff.
On Mon, Apr 30, 2012 at 9:05 AM, Slide wrote:
> This sounds like a great idea Jeff. Let me know if there is anything I
> can do to help out.
The "Extending and Embedding" section needs to be wiped out and
completely rewritten (since none of it applies to IronPython). I know
it's a lot to ask, but
This sounds like a great idea Jeff. Let me know if there is anything I
can do to help out.
Thanks,
slide
On Mon, Apr 30, 2012 at 8:57 AM, Jeff Hardy wrote:
> Here's what my thinking has been on documentation for the past little
> while. I just haven't had a chance to put it all together.
>
> Fi
Here's what my thinking has been on documentation for the past little
while. I just haven't had a chance to put it all together.
First off, there's a great site called readthedocs.org (RTD) that
hosts softwsre documentation (for free). I believe it works with any
sort of documentation if you set i
I noticed today that IronPython's codeplex page has an empty
"Documentation" tab. It just says: "There is no documentation yet." I
wish to fix that problem.
Is http://ironpython.net/documentation/ actually our official
documentation? If so, the site needs some updating. Who can do that?
Or is
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
On Fri, Jul 15, 2011 at 7:22 AM, Jimmy Schementi wrote:
>> Also, is the plan to stick with codeplex issues or possibly move to github's
>> issue system?
>>
>> slide
>
> Moving to GitHub might be nice, but we lose voting. In the past voting seemed
> to help. Anyways, I say we stay on CodePlex for
On Jul 15, 2011, at 10:15 AM, Slide wrote:
> How does one become a member of the project on codeplex so that issues can be
> assigned to them?
Send me your codeplex id and I'll add you as a developer.
> Also, is the plan to stick with codeplex issues or possibly move to github's
> issue system?
How does one become a member of the project on codeplex so that issues can
be assigned to them? Also, is the plan to stick with codeplex issues or
possibly move to github's issue system?
slide
--
slide-o-blog
http://slide-o-blog.blogspot.com/
___
Ironp
36 matches
Mail list logo
