Preparing for RubyConf
I’m trying to get back on the blog wagon, so I’m going to try and do more, shorter posts.
Anyways, the rubinius team is preparing for the preview release at rubyconf. We haven’t altered the development flow much, though I’m pushing people to get close their tickets for the release.
We moved over to using lighthouse for project track which is working out better for tracking the tickets, especially milestone wise.
At rubyconf, we’ll probably do some sanity checks on the git edge and then just cut a release directly from that. The stability is getting a lot better everyday, something I’m really happy with.
One reason I know it’s getting more stable is that I decided last week to totally start over on the rubinius compiler (the thing that converts ruby text into bytecode). I’ve totally reworked the architecture to be a lot more modular, faster, and much easier to test. I’ve been doing the development of this new compiler solely in rubinius (the original compiler was first built in MRI, like any good bootstrapped system). So far, I haven’t hit any bugs in rubinius while writing and testing compiler2. This fact makes me all warm and fuzzy inside.
See everyone at RubyConf!
