Ruby Hero Award is a great initiative to highlight some of all the hard-working people in the Ruby and Rails communities who might otherwise not get as much exposure as their work deserves. So go on an nominate your favorite hacker and let’s celebrate the many great people doing good stuff.
Due to a snafu at the domain company holding rubyonrails.org, the site was turned into their default Google-baiting holding spot yesterday. The problem has now been resolved and the Google-bait has been eradicated. Sorry for the scare.
Lighthouse “version 2” deployed yesterday, so I’m officially opening the Rails Lighthouse tracker up for business. Other spinoff projects such as Prototype and Capistrano have already made the switch. As David has mentioned, this means the current trac instance is deprecated. It will continue to stay in use for now until everyone has transitioned to Lighthouse.
We’re still figuring out the new workflow with git, Github, and Lighthouse. I’ll be working with the Logical Awesome folks to improve the Lighthouse/Github relationship. I’m also working with Tim Pope (author of the awesome git-trac tool) and others in #rails-contrib on bringing the same development tools to the new git infrastructure. Tim also wrote some best practices for contributing to Rails from git.
Geoff Buesing has writing a great guide to the time zone support in Rails 2.1. It goes through all the new features including how to setup per-user time zone support and more. Really good stuff. Geoff’s work will remove a lot of pain for a lot of people. Three cheers to his hard work.
The guys at Phusion has finally wrapped up Passenger, their mod_rails-like module for Apache. It’s looking like a great, easy solution for people who want a more PHP-like deployment story. Just dump your files in a directory setup with a vhost and off you go. Touch tmp/restart.txt and the application is restarted. Doesn’t get much simpler than that.
If you don’t have git, or don’t enjoy running it on your platform, you need not fear. We’ve set up an automated task to produce a zip file of Rails Edge that’ll be kept up to date all the time: http://dev.rubyonrails.org/archives/rails_edge.zip. This is also what we’ve made the new rake rails:freeze:edge use.
This also means that development on the Subversion repository has stopped and will no longer be kept up to date. We’ll keep the Subversion repository around for some time for people to transition off svn:externals, though. But if you want the latest edge, you’ll have to use either git or the new zip files.
We’ll also soon go live with our new ticket management system, which will be running on a new version of Lighthouse. When that happens, the Trac installation will follow the Subversion repository into legacy. We’ll still keep it around so we can work through all the patches and tickets that are there, but everything new will happen on the Lighthouse setup.
We hope you’ll enjoy this upgrade to the Rails collaboration infrastructure. We’re really looking forward to the onslaught of marvelous patches that the Git lords have promised us will flow from the mountain now.
The session schedule for RailsConf is now available. A very packed lineup across Thursday through Sunday.
Also, the early bird deal is ending April 10th. After that, the price of admission will jump another $100. So if you’re planning to go, getting your ticket before April 10th would be an easy way to save a Benjamin.
There seem to be some confusion over what the core development of Rails on Git will mean to Windows users. The simple answer is: Absolutely nothing. But let me give you a slightly more involved answer:
- rake rails:freeze:edge will still work. We’ll make it use either zip or tar.gz files. It’ll actually be even better as it won’t even require a SCM to work.
- Tickets will still accept regular patches that you can create with any diff tool.
So this will mean no difference to users of Rails and it’ll mean no difference to developers of Rails. What it will mean is that people who are interested in using Git (which again does come in a variety of flavors for Windows despite not being as well-supported as on nix) will get some value-added features in form of easier branching and the other Git goodies.
If you’re freaking out, calm down. Rails and the developers behind it have snubbed Windows far, far worse in the past :). The original release of the framework didn’t even run on Windows. This move to Git is not a snub.
We’ve been preparing for Rails to move the official source repository from Subversion to Git for some time now and it seems that it’ll happen over the next week or so. The premiere will happen alongside the official launch of Github.
The move will also mean that we’re going to be switching ticket tracking to Lighthouse. So now both our repository and ticket tracking will be powered by Rails applications, which is a nice bonus treat.
When the move happens, we’ll freeze the existing Subversion repository and the Trac installation. Both will live on for a long time to come, but will be entirely deprecated. This means that your existing svn:externals will not break, but if you want the latest edge, you’ll have to get it from the new git repository.
So now is a great time to learn more about Git in anticipation of this move. I recommend starting with the Git for SVN’ers crash course.
Rails 2.1 is not far off the horizon and we’ve been adding a ton of extra deliciously nice goodies in preparation of its release lately. As always, the good Ryan Daigle has been keeping a watchful eye on the changelog and has been documenting some of the new features. The latest stars are: