Thanks guys. I've opened up a PR <https://github.com/rails/rails/pull/23218>. Let's see what happens :)
On Sunday, 24 January 2016 13:36:02 UTC, Ken Collins wrote: > > That is a great point too. I can see both sides. But looking at the memory > decrease as a "feature" seems like a winner to me to at least try to go ~> > 2.6 for the initial release of Rails 5. > > - Ken > > On January 24, 2016 at 8:25:07 AM, Karl Freeman ([email protected] > <javascript:>) wrote: > > That's a solid point. I don't really have a response other than because of > the benefits above and the opportunity of doing this during a major release > (e.g when people are already upgrading gems). Logically, in my head seeing > a memory decrease during a major release of Rails by being progressive with > a non breaking dependency makes it worth ~> 2.6 > > > No harm either way as eventually, people will catch this update :). > > -- > 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 [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
