When does Rails 3.2 reach end-of-life?

Now that Rails 4.2 has been released, does anyone know when Rails 3.2 reaches end-of-life?

Looking at their Maintenance policy (http://guides.rubyonrails.org/maintenance_policy.html ) it appears 3.2 will no longer receive bug fixes or security updates (only severe security updates). So, I would assume 3.2 is effectively already end-of-life at this time. Please let me know if this is not correct.

From their 4.2 release notes (http://weblog.rubyonrails.org/2014/12/19/Rails-4-2-final/ ) it appears Rails 3.2 will be EOL when 5.0 comes out sometime in summer 2015.

I can't actually see where it is stated that 3.2 will reach EOL.

Colin

I can’t actually see where it is stated that 3.2 will reach EOL.

Looking at their older maintenance policies, the last version to receive only severe security upgrades is usually abandoned with the next public release: http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/

Current maintenance policy for comparison: http://guides.rubyonrails.org/maintenance_policy.html

I can’t actually see where it is stated that 3.2 will reach EOL.

Historically, from thrir older maintenance policies, the oldest version to receive only severe security updates is generally dropped from receiving any updates with the next public release e.g. for Rails 3.1:

http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/

I can't actually see where it is stated that 3.2 will reach EOL.

Historically, from thrir older maintenance policies, the oldest version to
receive only severe security updates is generally dropped from receiving any
updates with the next public release e.g. for Rails 3.1:
http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/

OK, thanks.

Colin