On Wed, Feb 9, 2011 at 11:35 AM, Ken Collins <[email protected]> wrote: > > When calls were made to test 3.0.4.rc1, I followed up a few days afterward > for the latest SQL Server adapter. Santiago was nice enough to pick up on my > ticket for a calculation bug [1] and got it committed to master [2] and then > 3-0-stable [3] so it can make it in the next release. I just ran my test > suite on the tag of the repo and it appears these did not make it in the > v3.0.4 release. How did that happen? Is there anything else that did not make > it in?
The 3.0.4 final release was the 3.0.4rc1 + the security fixes. Nothing else. Your stuff wasn't a release blocker so it was left out. We can do a 3.0.5 release in a week or so to catch any other issues that get noticed in the interim, I just felt that it was more important we get the 3.0.4 release out with no risk of additional regressions given the severity of the CSRF bug. -- Cheers Koz -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
