That's awesome, thanks. I'll steal what I can to set it up for real when I get a chance (sadly, probably not until next year). Tests will be harder, since I want the test infrastructure to be capable of running for Xamarin (iOS/Android) and UWP (or whatever it is by the time I get around to it.) At least for the core language tests.
- Jeff On Mon, Nov 16, 2015 at 1:26 PM, Tim Orling <ticot...@gmail.com> wrote: > > On Mon, Nov 16, 2015 at 1:08 PM, Tim Orling <ticot...@gmail.com> wrote: > >> >> >> On Mon, Nov 9, 2015 at 2:40 PM, Jeff Hardy <jdha...@gmail.com> wrote: >> >>> >>> >>> On Thu, Nov 5, 2015 at 9:41 PM, Tim Orling <ticot...@gmail.com> wrote: >>> >>>> >>>> >>>> On Nov 5, 2015, at 9:14 PM, Jeff Hardy <jdha...@gmail.com> wrote: >>>> >>>> On Thu, Nov 5, 2015 at 12:55 AM, Kuno Meyer <kuno.me...@gmx.ch> wrote: >>>> >>>>> First, I would start processing pending pull requests and react to bug >>>>> reports on Github (merge / give feedback). A project that has virtually >>>>> lost all active core developers and that nobody feels responsible to >>>>> create >>>>> roadmaps and to drive releases is not very likely to attract new >>>>> developers. >>>>> >>>>> Then, and maybe I've missed that, there should be an official >>>>> statement about the healthiness of the 3.0 branch (compared to the 2.7 >>>>> branch) and about where checkins should go. >>>>> >>>>> And finally, it would be very helpful if some "official" test suite >>>>> results would be accessible somewhere, so that any developer can easily >>>>> see >>>>> which of the red tests are actually due to his changes. >>>>> >>>>> Just my 2 cents. I am using IronPython on a daily basis, but the >>>>> current situation makes it hard to recommend it to anybody else. >>>>> >>>> >>>> Agree with all of this. I'll try to be better about checking on PRs >>>> within a couple of days instead of letting them linger. >>>> >>>> I have a half-written blog post on IronPython status to remind people >>>> that it's not dead. :) Posting the test suite results is a good idea, and >>>> the teamcity server used to have them, but the test suite also needs a lot >>>> of work to pass cleanly. >>>> >>>> >>>> How about having CI and the tests running on AppVeyor? I'll help with >>>> that. >>>> >>> >>> If you can get it running that would be great. I looked at it a while >>> back it seemed simple enough. >>> >> >> First crack at it: >> https://ci.appveyor.com/project/moto-timo/ironpython3 >> >> The appveyor.yml is dead simple: >> build_script: - .\make.cmd >> >> Note that this required a pending PR ( >> https://github.com/IronLanguages/ironpython3/pull/58). >> >> This doesn't run any tests nor try to deploy. AppVeyor has a hard limit >> of 30 minutes per build (50 minutes for enterprise). I will be working on >> getting tests running next and see if we break the time limit. >> >> For deploying, it gets more complicated because you must have admin >> rights to the github project in order to set at least one global >> environment variable. >> >> I'll also add the "badges" to my fork's Readme so you can see how that >> works. >> >> I also plan to go back to IronPython 2.7 branch for the same... although >> I would rather we spend our energy to push forward on IronPython 3 :) >> > > I also got Travis CI building with mono: > https://travis-ci.org/moto-timo/ironpython3 > > The .travis.yml is likewise dead simple: > > language: csharpscript: - make > > >> >> >>> >>> >>>> >>>> Still, I know it's frustrating to only have radio silence form the core >>>> devs, but I can only say "sorry, to busy with real life" so many times >>>> before it starts to lose all meaning. It's been a very busy year for me; >>>> next year should be better, hopefully. >>>> >>>> Sounds like my life. How did we get so busy? >>>> >>> >>> In my case, family, friends, work - I think it's what old people call >>> "growing up". :) >>> >> >> Indeed. >> >> --Tim >> >> >
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
