Thanks for the great work. After every release I wonder what's next. Is there some sort of roadmap?
Rails 3.1 Gem Available
31–40 of 40 posts
Re: Rails 3.1 Gem Available
#32Yes, I am very excited. I should have released during business hours with announcements prepared and whatnot, but I really wanted this code in people's hands. I hope that everyone enjoys this release!
Thanks for all the hard work. You guys are awesome. BTW, it is business hours in India. :-)
Re: Rails 3.1 Gem Available
#33Yes, I am very excited. I should have released during business hours with announcements prepared and whatnot, but I really wanted this code in people's hands. I hope that everyone enjoys this release!
Thanks for all the hard work. You guys are awesome. BTW, it is business hours in India. :-)
Today is a holiday in India. :-)
Re: Rails 3.1 Gem Available
#34Fantastic!
Any particular reasn to only list DHH under "Authors"? (I assume the plural means more are possible...)
Perhaps a link to http://contributors.rubyonrails.org/ ?
Interestingly DHH is only #2 contrubutor overall, and number 9 this year... (by number of commits; and no, that isn't a perfect measure of contribution)
Re: Rails 3.1 Gem Available
#35I'm hesitant to give up on Jammit, but asset pipeline looks great.
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than it's the default in Rails 3.1 -- I'd be curious to hear about why. I'd like to keep developing Jammit as an alternative approach, as there are differences in philosophy: explicit asset packages vs. in-file dependencies, for example.
Re: Rails 3.1 Gem Available
#36Yes, I am very excited. I should have released during business hours with announcements prepared and whatnot, but I really wanted this code in people's hands. I hope that everyone enjoys this release!
I understand your excitement. I've been watching your work on it! You deserve a nice, long vacation, man.
Thank you.
Re: Rails 3.1 Gem Available
#37I'm hesitant to give up on Jammit, but asset pipeline looks great.
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than it's the default in Rails 3.1 -- I'd be curious to hear about why. I'd like to keep developing Jammit as an alternative approach, as there are differences in philosophy: explicit asset packages vs. in-file dependencies, for example.
Jammit has worked extremely well paired with Barista+Compass, but for a Backbone-heavy app where templates are shipped client-side, it's nice to tack on '.erb' at the end of a template file and use Rails asset helpers for cache-busting and asset host url construction.
Re: Rails 3.1 Gem Available
#38Earlier quoted context omitted.
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than it's the default in Rails 3.1 -- I'd be curious to hear about why. I'd like to keep developing Jammit as an alternative approach, as there are differences in philosophy: explicit asset packages vs. in-file dependencies, for example.
Jammit has worked extremely well paired with Barista+Compass, but for a Backbone-heavy app where templates are shipped client-side, it's nice to tack on '.erb' at the end of a template file and use Rails asset helpers for cache-busting and asset host url construction.
Jammit should already be playing well with Rails' built-in cache busting, although I imagine that the situation might change with 3.1's new fingerprinting.
As for having to pipe "static" JS and CSS files through ERB ... I've always thought that was something best avoided by choice, unless absolutely necessary.
Re: Rails 3.1 Gem Available
#39Thanks to Rails core and all the contributors for yet another killer release :) If you're new to 3.1, the following resources will help you to get started: Release notes: http://guides.rubyonrails.org/3_1_release_notes.html Asset pipeline: http://guides.rubyonrails.org/asset_pipeline.html http://railscasts.com/episodes/279-understanding-the-asset-p...
Thanks for the links. From reading the release notes, it looks like there's a lot of changes around the behavior of creating/updating/destroying through active record associations - other than the release notes is there anywhere else that has a good writeup of these changes?
Re: Rails 3.1 Gem Available
#40Here is something not in the release notes that people may want to watch out for: The format of the session has changed, the FlashHash class to be precise, so trying to load a browser session created on Rails 3.0 will give a marshal load error on 3.1 if it had anything in the flash.
This means you will want to change your SESSION_KEY variable to expire all sessions, otherwise users that are logged in while you upgrade can get stuck until they clear their cookies. (So I postponed the upgrade to the weekend...)