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 <jdha...@gmail.com> wrote: > On Fri, Mar 21, 2014 at 4:28 PM, Slide <slide.o....@gmail.com> 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 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. >> > > Closing isn't a big deal; one thing the CodePlex site does well is let you > bulk-update 100 tickets at a time. > > My thought is to close them all with a message similar to Keith's > suggestion and then leave one open issue redirecting people to the GH > issues page. > > - Jeff > > > >> >> >> On Fri, Mar 21, 2014 at 9:14 AM, Keith Rome <r...@wintellect.com> wrote: >> >>> 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" would be enough to catch the things that fall through the cracks. >>> >>> >>> *Keith Rome* >>> >>> *Principal Architect @ Wintellect (www.wintellect.com >>> <http://www.wintellect.com>)* >>> >>> 770.617.4016 | kr...@wintellect.com <r...@wintellect.com> >>> >>> >>> >>> >>> Register today <https://www.wintellectnow.com/Account/Promo/ROME-13> for >>> access to our high-quality on-demand training resources! >>> >>> >>> From: Jeff Hardy <jdha...@gmail.com> >>> Date: Friday, March 21, 2014 at 9:39 AM >>> To: Slide <slide.o....@gmail.com> >>> Cc: "ironpython-users@python.org" <ironpython-users@python.org> >>> Subject: Re: [Ironpython-users] CodePlex Issues (Was: IronPython 3 >>> Update) >>> >>> On Fri, Mar 21, 2014 at 1:33 PM, Slide <slide.o....@gmail.com> 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) that would be really nice to get rid of since we don't >>> have the infrastructure to replicate them. I'm up for anything, just >>> need to >>> update my tool to add date and vote filtering if we decide to go that >>> route. >>> >>> >>> Yeah, we're going to lose some good, actionable issues, but I think >>> it's acceptable. The 1000+ issues currently open are just too many to >>> do anything useful with. I'm curious to see how many issues we would >>> be talking about with the given criteria - around 250 would be good, >>> but that's just a gut feeling. >>> >>> - Jeff >>> _______________________________________________ >>> Ironpython-users mailing list >>> Ironpython-users@python.org >>> https://mail.python.org/mailman/listinfo/ironpython-users >>> >>> >> >> >> -- >> Website: http://earl-of-code.com >> > > -- Website: http://earl-of-code.com
<<inline: 529A2558-817C-467F-8E7E-0789B90D675C[9].png>>
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
