Comments on: The Incredible Rising Version Number http://pathfindersoftware.com/2009/02/the-incredible-rising-version-number/ The Fastest Way to Launch Successful Software Thu, 19 Jan 2012 16:36:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ruby on Rails » Keeping Up With The Joneses: Keeping Rails and its extensions up to date » Pathfinder Development http://pathfindersoftware.com/2009/02/the-incredible-rising-version-number/#comment-9278 Ruby on Rails » Keeping Up With The Joneses: Keeping Rails and its extensions up to date » Pathfinder Development Fri, 06 Mar 2009 18:00:35 +0000 http://www.pathf.com/blogs/?p=1397#comment-9278 [...] post is the practical companion to my post about a month ago about keeping up with Edge Rails and new versions. There are many wonderful things about Rails and [...] [...] post is the practical companion to my post about a month ago about keeping up with Edge Rails and new versions. There are many wonderful things about Rails and [...]

]]> By: Jason Seifer http://pathfindersoftware.com/2009/02/the-incredible-rising-version-number/#comment-9277 Jason Seifer Tue, 10 Feb 2009 00:18:13 +0000 http://www.pathf.com/blogs/?p=1397#comment-9277 Thanks a lot for the podcast mention! I agree with you mostly about the different versions of Rails to use. One thing I'd like to add is that if you're using RSpec for testing, it's generally a good idea to stay away from edge if you plan on updating edge frequently. I've lost a lot of time from a broken edge RSpec/Rails combination. HOWEVER, the good news is that keeping RSpec working with edge is going to be much more of a priority from now on, according to Yehuda. Anyway, great post! Thanks a lot for the podcast mention! I agree with you mostly about the different versions of Rails to use. One thing I’d like to add is that if you’re using RSpec for testing, it’s generally a good idea to stay away from edge if you plan on updating edge frequently. I’ve lost a lot of time from a broken edge RSpec/Rails combination. HOWEVER, the good news is that keeping RSpec working with edge is going to be much more of a priority from now on, according to Yehuda. Anyway, great post!

]]> By: Antares Trader http://pathfindersoftware.com/2009/02/the-incredible-rising-version-number/#comment-9276 Antares Trader Mon, 09 Feb 2009 19:40:03 +0000 http://www.pathf.com/blogs/?p=1397#comment-9276 "Point release updates (2.0 -> 2.1) generally should not be applied to an app in production unless other work is going on." Hopefully this is going to change in Rails 3.0 as the design teem has committed to a stable and tested public API like Merb has. This should help projects stay compatible with point releases as long as they follow the API and don't Monkey Patch things too much. On a related Note, here hoping that Rails 3.0 will also be easier to extend (a la Merb). “Point release updates (2.0 -> 2.1) generally should not be applied to an app in production unless other work is going on.”

Hopefully this is going to change in Rails 3.0 as the design teem has committed to a stable and tested public API like Merb has. This should help projects stay compatible with point releases as long as they follow the API and don’t Monkey Patch things too much.

On a related Note, here hoping that Rails 3.0 will also be easier to extend (a la Merb).

]]>