I've submitted a patch and test: http://dev.rubyonrails.org/ticket/11162
Review and verification is much appreciated.
I've applied this to stable now, could people please test and report back.
I've submitted a patch and test: http://dev.rubyonrails.org/ticket/11162
Review and verification is much appreciated.
I've applied this to stable now, could people please test and report back.
Any chance of http://dev.rubyonrails.org/ticket/10980 making it to stable? I'd say it's a pretty crucial fix. It was fixed in the following changeset: http://dev.rubyonrails.org/changeset/8787.
Isn’t this a feature change?
> Any chance of http://dev.rubyonrails.org/ticket/10980 making it to > stable? I'd say it's a pretty crucial fix. It was fixed in the following > changeset: http://dev.rubyonrails.org/changeset/8787.
Isn't this a feature change?
Yeah, it's not going to be backported. Load order changes like that can have unpredictable impacts on people's applications.
Hey,
I've played around a bit more with the stable branch and hit an issue with Enumerable#group_by. The implementation in 2.0.2 returns a hash, the 2-0-stable branch returns an array. See http://dev.rubyonrails.org/changeset/8605
This has been changed again to an OrderedHash in trunk. See http://dev.rubyonrails.org/changeset/8700
Simplest solution would be to backport r8700, worst case scenario r8605 can be rolled back.
Cheers,
Menno
I merged the OrderedHash changes into 2-0-stable, Is your app all clear now?
Alexey, any progress on a CI rig for stable? ![]()