Rails 1.2
Woopee Do
Rails 1.2 is out. This means I will be upgrading this box to use it just as soon as I've run all the tests on all the sites it's hosting, and made sure that everything works. All three of them.
Amongst the changes are REST controllery thingies, as you can tell from the above link, and some plugin changes that have a knock on effect for Rails Engines users. There are a few deprecated features that should provide work for idle hands.
It will be interesting to see how it changes the way we develop at work. It looks as though the REST stuff will suggest a more natural way to separate controllers.
Rails Engines 1.2
If you're an engines user, you should be using Rails Engines 1.2.0, which is designed for Rails 1.2. It includes a much-needed fix for the migrations-in-engines-synchronisation problem. That is, how to do migrations in a specific order across the application and each engine. It is solved by running the following command from RAILS_ROOT whenever an engine migration is added:
script/generate plugin_migration
This creates a migration that brings the application's database up to the current engines' migration versions.
Word of Warning
After writing the above, I've tried an upgrade of this site. From this I have concluded the following:
it's no simple task to upgrade your apps to 1.2.1
There is apparently no official documentation on doing so. I'll post here once I've cracked how to do it. For this site, it looks like I might be recreating everything from a fresh Rails app. Something tells me that's not going to cut it for headline projects at work...
Geek Update
Just in case you didn't get it, this is a geek update.