Switching from Edge Rails to 1.2 stable with Piston

Update 1/25/07: Francois pointed out that now as of Piston 1.3.0 you can now do this all with the following command:

piston switch http://dev.rubyonrails.org/svn/rails/tags/rel_1-2-1 vendor/rails

For starters, if you’re still using svn:externals to manage your vendor/rails directory it’s time to switch to using Piston. svn:externals is so Q4!

However, if you’re already running Piston, now that Rails 1.2 is out you may want to switch from running Edge (the trunk or head branch) to the stable 1.2 release for your production applications. Here’s how to make the switch with Subversion and Piston:

cd your_app
# Remove the old Piston checkout
svn delete vendor/rails
svn commit -m "Deleted edge" vendor/rails
svn update
# Checkout 1.2.1 (or newer)
piston import http://dev.rubyonrails.org/svn/rails/tags/rel_1-2-1 vendor/rails
svn commit -m "Rails 1.2.1" vendor/rails
This entry was posted in Ruby, Ruby on Rails, Source Control. Bookmark the permalink.

One Response to Switching from Edge Rails to 1.2 stable with Piston

  1. Hello Todd,

    You might want to read this: http://blog.teksol.info/articles/2007/01/22/piston-1-3-0-switch-goodness

    Piston 1.3.0 now supports the switch subcommand, allowing you to do:
    piston switch http://dev.rubyonrails.org/svn/rails/tags/rel_1-2-1 vendor\rails

    Bye !

Comments are closed.