Hi everyone,
Rails 3.2.8.rc2 has been released. If no regressions are found we will
release 3.2.8 final around Wednesday 8th.
## IMPORTANT
We are removing all the deprecation warnings that we introduced in 3.2.x.
We have decided to stop introducing API deprecations in all point
releases going forward. From now on, it''ll only happen in
majors/minors.
## CHANGES since 3.2.8.rc1
*ActionMailer*
* No changes
*ActionPack*
* html_escape should escape single quotes. *Santiago Pastorino*
*ActiveModel*
* No changes
*ActiveRecord*
* Do not set RAILS_ENV to "development" when using `db:test:prepare`
and related rake tasks.
This was causing the truncation of the development database data
when using RSpec.
In RC2 was fixed again when using config.active_record.schema_format = :sql
*Rafael Mendonça França*
* Do not consider the numeric attribute as changed if the old value
is zero and the new value is not a string. Fixes #7237. *Rafael
Mendonça França*
*ActiveResource*
* No changes
*ActiveSupport*
* Fix ActiveSupport integration with Mocha > 0.12.1. *Mike Gunderloy*
*Railties*
* ERB scaffold generator use the `:data => { :confirm =>
"Text" }`
syntax instead of `:confirm`. *Rafael Mendonça França*
## SHA-1
* 351b13c792517534b68df02f550cfc335c8d3f5f actionmailer-3.2.8.rc2.gem
* 0b0f92bb3f2fad426f3b9c0849e5f5457c029586 actionpack-3.2.8.rc2.gem
* c19868c2f4fc20ebf20c1a27c89a65b80592b6e6 activemodel-3.2.8.rc2.gem
* 9d247e14feb6d453aded4ba9edc8bae1cf940891 activerecord-3.2.8.rc2.gem
* 7db76b428fdec2aeea190773d5daea139c7732ba activeresource-3.2.8.rc2.gem
* b93d62722c854fde8acda511f53481c4f3ceeaf2 activesupport-3.2.8.rc2.gem
* 7fd2e2035469e89e17b3872d51968a5856d6ed8c rails-3.2.8.rc2.gem
* bf685a73a55fd5ffa77c7c0160b2bec898fa15eb railties-3.2.8.rc2.gem
You can find a list of changes between v3.2.8.rc1 and v3.2.8.rc2
[here](https://github.com/rails/rails/compare/v3.2.8.rc1...v3.2.8.rc2)
and an exhaustive list of changes since v3.2.7
[here](https://github.com/rails/rails/compare/v3.2.7...v3.2.8.rc2).
Please let us know if your test suites are fine with this release or not.
Thanks to everyone!
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
Our test suite (rspec/capybara+webkit/jasmine) which was broken by 3.2.7 is working perfectly in 3.2.8.rc2. Thanks! --Daniel Evans On Friday, August 3, 2012 8:29:57 AM UTC-6, Santiago Pastorino wrote:> > Hi everyone, > > Rails 3.2.8.rc2 has been released. If no regressions are found we will > release 3.2.8 final around Wednesday 8th. > > ## IMPORTANT > > We are removing all the deprecation warnings that we introduced in 3.2.x. > We have decided to stop introducing API deprecations in all point > releases going forward. From now on, it''ll only happen in > majors/minors. > > ## CHANGES since 3.2.8.rc1 > > *ActionMailer* > > * No changes > > > *ActionPack* > > * html_escape should escape single quotes. *Santiago Pastorino* > > > *ActiveModel* > > * No changes > > > *ActiveRecord* > > * Do not set RAILS_ENV to "development" when using `db:test:prepare` > and related rake tasks. > This was causing the truncation of the development database data > when using RSpec. > In RC2 was fixed again when using config.active_record.schema_format = > :sql > *Rafael Mendonça França* > > * Do not consider the numeric attribute as changed if the old value > is zero and the new value is not a string. Fixes #7237. *Rafael > Mendonça França* > > > *ActiveResource* > > * No changes > > > *ActiveSupport* > > * Fix ActiveSupport integration with Mocha > 0.12.1. *Mike Gunderloy* > > > *Railties* > > * ERB scaffold generator use the `:data => { :confirm => "Text" }` > syntax instead of `:confirm`. *Rafael Mendonça França* > > > ## SHA-1 > > * 351b13c792517534b68df02f550cfc335c8d3f5f actionmailer-3.2.8.rc2.gem > * 0b0f92bb3f2fad426f3b9c0849e5f5457c029586 actionpack-3.2.8.rc2.gem > * c19868c2f4fc20ebf20c1a27c89a65b80592b6e6 activemodel-3.2.8.rc2.gem > * 9d247e14feb6d453aded4ba9edc8bae1cf940891 activerecord-3.2.8.rc2.gem > * 7db76b428fdec2aeea190773d5daea139c7732ba activeresource-3.2.8.rc2.gem > * b93d62722c854fde8acda511f53481c4f3ceeaf2 activesupport-3.2.8.rc2.gem > * 7fd2e2035469e89e17b3872d51968a5856d6ed8c rails-3.2.8.rc2.gem > * bf685a73a55fd5ffa77c7c0160b2bec898fa15eb railties-3.2.8.rc2.gem > > You can find a list of changes between v3.2.8.rc1 and v3.2.8.rc2 > [here](https://github.com/rails/rails/compare/v3.2.8.rc1...v3.2.8.rc2) > and an exhaustive list of changes since v3.2.7 > [here](https://github.com/rails/rails/compare/v3.2.7...v3.2.8.rc2). > > Please let us know if your test suites are fine with this release or not. > > Thanks to everyone! > > -- > > Santiago Pastorino > WyeWorks Co-founder > http://www.wyeworks.com > > Twitter: http://twitter.com/spastorino > Github: http://github.com/spastorino >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/B3g6e6DuZLAJ. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Friday, August 3, 2012 4:29:57 PM UTC+2, Santiago Pastorino wrote:> We are removing all the deprecation warnings that we introduced in 3.2.x. > We have decided to stop introducing API deprecations in all point > releases going forward. From now on, it''ll only happen in > majors/minors. >Does this mean that all deprecation warnings will appear in releases X.Y.0 and disappear in X.Y.1 ? I like this idea. - Alexey. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/TM7tEvKyfZcJ. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On 04/08/12 12:48, Alexey wrote:> > On Friday, August 3, 2012 4:29:57 PM UTC+2, Santiago Pastorino wrote: > > We are removing all the deprecation warnings that we introduced in > 3.2.x. > We have decided to stop introducing API deprecations in all point > releases going forward. From now on, it''ll only happen in > majors/minors. > > > Does this mean that all deprecation warnings will appear in releases > X.Y.0 and disappear in X.Y.1 ? I like this idea.No. New deprecation warnings will only be added in X.Y.0, but the deprecated feature itself will not be removed until X.Z.0. -- http://jonathanleighton.com/ -- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Saturday, August 4, 2012 9:41:54 PM UTC+9:30, Jon Leighton wrote:> On 04/08/12 12:48, Alexey wrote: > > > > > > On Friday, August 3, 2012 4:29:57 PM UTC+2, Santiago Pastorino wrote: > > > > > > We are removing all the deprecation warnings that we introduced in > > > 3.2.x. > > > We have decided to stop introducing API deprecations in all point > > > releases going forward. From now on, it''ll only happen in > > > majors/minors. > > > > > > > > > Does this mean that all deprecation warnings will appear in releases > > > X.Y.0 and disappear in X.Y.1 ? I like this idea. > > > > No. New deprecation warnings will only be added in X.Y.0, but the > > deprecated feature itself will not be removed until X.Z.0. > > > > -- > > http://jonathanleighton.com/I know I might be being a bit pedantic, but is Z > Y? is Z = Y+1? I read it as: There may be deprecation warnings added in X.Y.0 which will stay ''frozen'' until X.Y+1.0 , so any X.Y.a release will not have deprecation warnings added (a!=0). Although I''m not sure if they will get removed in version X.Y+1.0 or some X.Y+N.0 release. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/PC-Tefs8rr4J. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Rails 3.2.1 won''t add any deprecation warnings anymore, but 3.3 will. Currently, we expect to add deprecation warnings only on 4.0. If we decide to deprecate something, 4.0.x won''t have any warnings, but 4.1.0 will. On Tue, Aug 28, 2012 at 8:36 PM, niko malessa <niko.malessa@gmail.com>wrote:> On Saturday, August 4, 2012 9:41:54 PM UTC+9:30, Jon Leighton wrote: > > On 04/08/12 12:48, Alexey wrote: > > > > > > > > > > On Friday, August 3, 2012 4:29:57 PM UTC+2, Santiago Pastorino wrote: > > > > > > > > > > We are removing all the deprecation warnings that we introduced in > > > > > 3.2.x. > > > > > We have decided to stop introducing API deprecations in all point > > > > > releases going forward. From now on, it''ll only happen in > > > > > majors/minors. > > > > > > > > > > > > > > > Does this mean that all deprecation warnings will appear in releases > > > > > X.Y.0 and disappear in X.Y.1 ? I like this idea. > > > > > > > > No. New deprecation warnings will only be added in X.Y.0, but the > > > > deprecated feature itself will not be removed until X.Z.0. > > > > > > > > -- > > > > http://jonathanleighton.com/ > > I know I might be being a bit pedantic, but is Z > Y? is Z = Y+1? > > I read it as: There may be deprecation warnings added in X.Y.0 which will > stay ''frozen'' until X.Y+1.0 , so any X.Y.a release will not have > deprecation warnings added (a!=0). > > Although I''m not sure if they will get removed in version X.Y+1.0 or some > X.Y+N.0 release. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/PC-Tefs8rr4J. > To post to this group, send email to rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > >-- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.