My previous experience porting a 3.0 app to a 3.2 application wasn't too shabby in the end. 狢 only had to change application.rb and the rest was all asset pipeline related which just involved mostly moving files around and creating manifests for the Javacript files.<div> </div><div>-Eric</div><div class="gmail_extra"> <div class="gmail_quote">On Fri, Dec 7, 2012 at 12:15 PM, David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I thought I'd send a second email in case you guys happened to miss the first one. David <div class="HOEnZb"><div class="h5"> ----- Original Message ----- > From: "David Davis" <<a href="mailto:daviddavis@redhat.com">daviddavis@redhat.com</a>> > To: <a href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> > Sent: Friday, December 7, 2012 12:03:20 PM > Subject: [katello-devel] Rails 3.2 features > > I just wanted to make a list of features that we'll get upgrading to > Rails 3.2. I'm sending these out to inform everyone but I think it's > worth reiterating that it's going to be painful to upgrade. It won't > be as bad as going from Rails 2 to Rails 3 but it's not going to be > easy either. Without futher ado... > > * Probably the biggest thing is the asset pipeline. It does > everything from compiling languages (like SASS) to uglifying js > code. Check out more info at > <a href="http://guides.rubyonrails.org/asset_pipeline.html" target="_blank">http://guides.rubyonrails.org/asset_pipeline.html</a> > * New migration features. You no longer have to write up/down methods > for the most part. Instead you just write "change" methods. More > info at <a href="http://guides.rubyonrails.org/migrations.html" target="_blank">http://guides.rubyonrails.org/migrations.html</a> > * Multiple levels of has_many :through > * Create key value stores in the database > (<a href="http://blog.rawonrails.com/2012/02/using-activerecordstore-with-rails-32.html" target="_blank">http://blog.rawonrails.com/2012/02/using-activerecordstore-with-rails-32.html</a>) > * New active record methods like pluck > (<a href="http://api.rubyonrails.org/classes/ActiveRecord/Calculations.html#method-i-pluck" target="_blank">http://api.rubyonrails.org/classes/ActiveRecord/Calculations.html#method-i-pluck</a>) > * Scoped mass assignment. Helpful for locking down attributes per > permission. > (<a href="http://launchware.com/articles/whats-new-in-edge-scoped-mass-assignment-in-rails-3-1" target="_blank">http://launchware.com/articles/whats-new-in-edge-scoped-mass-assignment-in-rails-3-1</a>) > * Slow query logger > <a href="http://weblog.rubyonrails.org/2011/12/6/what-s-new-in-edge-rails-explain/" target="_blank">http://weblog.rubyonrails.org/2011/12/6/what-s-new-in-edge-rails-explain/</a>. > I've used <a href="http://explain.depesz.com/" target="_blank">http://explain.depesz.com/</a> to help analyze query explain > output from postgres. > * Encrypted fields (passwords, etc) > <a href="http://railscasts.com/episodes/270-authentication-in-rails-3-1" target="_blank">http://railscasts.com/episodes/270-authentication-in-rails-3-1</a> > * New generator stuff. You can do "rails g scaffold Person name > email" instead of "rails g scaffold Person name:string > email:string". Or if you want to be really crafty: rails g scaffold > Person name:index email:uniq. > > David > > David > > _______________________________________________ > katello-devel mailing list > <a href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/katello-devel" target="_blank">https://www.redhat.com/mailman/listinfo/katello-devel</a> > _______________________________________________ katello-devel mailing list <a href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/katello-devel" target="_blank">https://www.redhat.com/mailman/listinfo/katello-devel</a> </div></div></blockquote></div> </div>