http://yanpritzker.com/2007/03/12/two-critical-patches-for-rails-122/ photographer, entrepreneur, software engineer, musician, skier Tue, 07 Sep 2010 15:00:04 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://yanpritzker.com/2007/03/12/two-critical-patches-for-rails-122/comment-page-1/#comment-3136 yan Mon, 12 Mar 2007 18:34:48 +0000 http://skwpspace.com/2007/03/12/two-critical-patches-for-rails-122/#comment-3136 First patch is no good in 1-2-stable. You guys applied a different patch which fixed the has_many through push but did not fix the delete. You should probably apply the patch that was actually attached to ticket 6466... First patch is no good in 1-2-stable. You guys applied a different patch which fixed the has_many through push but did not fix the delete. You should probably apply the patch that was actually attached to ticket 6466…

]]> http://yanpritzker.com/2007/03/12/two-critical-patches-for-rails-122/comment-page-1/#comment-3135 yan Mon, 12 Mar 2007 18:19:28 +0000 http://skwpspace.com/2007/03/12/two-critical-patches-for-rails-122/#comment-3135 I guess what was not clear to me is that I should be running 1-2-stable? My understanding is that if I wanted the latest rails I should be freezing TAG 1-2-2 because that was the last official announced release. I also assumed any critical errors such as the routing should be backpatched into that TAG? I guess what was not clear to me is that I should be running 1-2-stable? My understanding is that if I wanted the latest rails I should be freezing TAG 1-2-2 because that was the last official announced release. I also assumed any critical errors such as the routing should be backpatched into that TAG?

]]> http://yanpritzker.com/2007/03/12/two-critical-patches-for-rails-122/comment-page-1/#comment-3134 rick Mon, 12 Mar 2007 17:56:03 +0000 http://skwpspace.com/2007/03/12/two-critical-patches-for-rails-122/#comment-3134 The first patch was applied about a week ago, and the routing patch was applied 3 months ago. Looks like the routing patch didn't make it into the stable branch for whatever reason. You can always elevate these issues on the rails-core list. The first patch was applied about a week ago, and the routing patch was applied 3 months ago. Looks like the routing patch didn’t make it into the stable branch for whatever reason. You can always elevate these issues on the rails-core list.

]]>