IronPython/IronRuby have Decided on Github and CodePlex
- Share
-
- |
Read later
My Reading List
Since Microsoft announced that it was giving up control of its Iron languages, there has been a quiet debate on where to host the project. The negotiations have finally been settled and the winner is Github for source control and CodePlex for issue tracking.
Moving to Github allows the coordinators to better manage the large amount of code that overlaps both projects. These include the DLR itself as well as unit tests that address interoperability between the two languages. For those that prefer Mercurial to Git, there is a mirror on bitbucket.
Issue tracking will remain on CodePlex. It was decided that attempting to move the issue tracking over as well would be too disruptive at this time. Currently the IronPython team is asking for help in verifying the backlog of issues, many of which date back to version 1 and may have since been corrected.
Source Code Repositories
Issue Tracking
- IronPython - http://ironpython.codeplex.com/workitem/list/basic
- IronRuby - http://ironruby.codeplex.com/workitem/list/basic
- DLR - http://dlr.codeplex.com/workitem/list/basic
Educational Content
Concurrency in Clojure
Stuart Halloway May 17, 2013
Confessions of an Agile Addict
Ole Friis Østergaard May 16, 2013
Web Development: You're Doing It Wrong
Stefan Tilkov May 16, 2013
Programming The Feynman Way
Ben Evans May 15, 2013
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think