I opened a pull request on my changes:
https://github.com/rails/rails/pull/7800.
I updated the code a bit and fixed the tests so it is slightly different
than the branch referenced above. It should now be backward compatible with
older cache entries as well.
As for the Array idea, that would
On Sun, Sep 30, 2012 at 6:44 PM, Brian Durand
br...@embellishedvisions.comwrote:
I opened a pull request on my changes:
https://github.com/rails/rails/pull/7800.
I updated the code a bit and fixed the tests so it is slightly different
than the branch referenced above. It should now be
Mike,
We decided to do this for Rails 4.
Can you go ahead and provide a Pull Request?.
Mention me on it and I will merge.
Thanks again for putting all this ideas and for minitest-rails :)
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
On Sep 30, 2012, at 12:49 PM, Santiago Pastorino spastor...@gmail.com wrote:
Mike,
We decided to do this for Rails 4.
Can you go ahead and provide a Pull Request?.
Mention me on it and I will merge.
Thanks again for putting all this ideas and for minitest-rails :)
Awesome. Will do.
Is there any targeted date for release of Rails 4? Best I could find Googling
was in 2012, but that could mean anything from days to months.
Asking because I've been running across some obscure bugs
(https://github.com/rails/rails/issues/7809 for instance) in the course of a
larger patch, and
Soonish. There are some things that are blocking the release, but
they're being worked on. There's no set date. All the major pieces are
in place.
am curious if it would be better to split the bugs out as individual issues
(happens sooner) or fix them in a bigger patch (takes longer).
Always
On 1 October 2012 00:43, Steve Klabnik st...@steveklabnik.com wrote:
Soonish. There are some things that are blocking the release, but
they're being worked on. There's no set date. All the major pieces are
in place.
am curious if it would be better to split the bugs out as individual
