For a release there needs to be need. I.e. we won't just release the same code over and over, there needs to be meaningful patches. It also takes coordination and human power. Releasing is a non-trivial task. You can always use `github: 'rails/rails', branch: '4.2'` in your gemfile if you need more recent than whatever is currently released. If there is a HUGE patch that has been in master that you really really want then you need to help raise awareness. You could reply to the commit or PR where the patch was introduced, you could post on this list.
-- Richard Schneeman http://schneems.com On September 7, 2016 at 7:44:45 AM, James Coleman (jtc...@gmail.com) wrote: What is the process for determining when to release the next in the 4.2 series (4.2.8)? Is there a generally expected timeframe between releases? Or is it waiting on specific fixes? -- 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 https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
