We don't have plans to backport it. We worked to make upgrading to Rails 4.2 an easy task so it would not require to us maintain old Rails versions. That said I don't see a good reason to us maintain a backported feature. On Sep 2, 2014 12:23 PM, "Andrew Kane" <aceka...@gmail.com> wrote:
> Hey, > > Any plans to backport Active Job to earlier versions of Rails? This would > be super useful for external gems that do asynchronous tasks (exception > reporting, geocoding, etc). If not, I'll take a stab at it. > > Thanks, > Andrew > > [originally incorrectly posted in Ruby on Rails: Talk] > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
