Rails Setup

Rails Setup

  • Rails
  • Devise
  • GitHub

›Policies

Start Here

  • Getting Started with Rails
  • Development Dependencies Install

Models

  • Active Record Basics
  • Active Record Migrations
  • Active Record Validations
  • Active Record Callbacks
  • Active Record Associations
  • Active Record Query Interface
  • Multiple Databases with Active Record
  • Active Record and PostgreSQL

Views

  • Layouts and Rendering in Rails
  • Action View Overview
  • Action View Form Helpers

Controllers

  • Action Controller Overview
  • Rails Routing from the Outside In

Other Components

  • Active Support Core Extensions
  • Active Support Instrumentation
  • Action Mailer Basics
  • Action Mailbox Basics
  • Active Model Basics
  • Active Job Basics
  • Action Text Overview
  • Active Storage Overview
  • Action Cable Overview

Digging Deeper

  • Rails Internationalization (I18n) API
  • Testing Rails Applications
  • Securing Rails Applications
  • Debugging Rails Applications
  • Configuring Rails Applications
  • The Rails Command Line
  • The Asset Pipeline
  • Working with JavaScript in Rails
  • Autoloading and Reloading Constants
  • Caching with Rails: An Overview
  • Using Rails for API-only Applications
  • Threading and Code Execution in Rails
  • The Rails Initialization Process
  • Getting Started with Engines

Extending Rails

  • Rails on Rack
  • Creating and Customizing Rails Generators & Templates
  • Rails Application Templates
  • The Basics of Creating Rails Plugins

Contributions

  • Contributing to Ruby on Rails
  • API Documentation Guidelines
  • Ruby on Rails Guides Guidelines

Policies

  • Maintenance Policy for Ruby on Rails

Maintenance Policy for Ruby on Rails

Support of the Rails framework is divided into four groups: New features, bug fixes, security issues, and severe security issues. They are handled as follows, all versions in X.Y.Z format.


Rails follows a shifted version of semver:

Patch Z

Only bug fixes, no API changes, no new features. Except as necessary for security fixes.

Minor Y

New features, may contain API changes (Serve as major versions of Semver). Breaking changes are paired with deprecation notices in the previous minor or major release.

Major X

New features, will likely contain API changes. The difference between Rails' minor and major releases is the magnitude of breaking changes, and usually reserved for special occasions.

New Features

New features are only added to the master branch and will not be made available in point releases.

Bug Fixes

Only the latest release series will receive bug fixes. When enough bugs are fixed and its deemed worthy to release a new gem, this is the branch it happens from.

In special situations, where someone from the Core Team agrees to support more series, they are included in the list of supported series.

Currently included series: 5.2.Z.

Security Issues

The current release series and the next most recent one will receive patches and new versions in case of a security issue.

These releases are created by taking the last released version, applying the security patches, and releasing. Those patches are then applied to the end of the x-y-stable branch. For example, a theoretical 1.2.3 security release would be built from 1.2.2, and then added to the end of 1-2-stable. This means that security releases are easy to upgrade to if you're running the latest version of Rails.

Currently included series: 5.2.Z, 5.1.Z.

Severe Security Issues

For severe security issues all releases in the current major series, and also the last major release series will receive patches and new versions. The classification of the security issue is judged by the core team.

Currently included series: 5.2.Z, 5.1.Z, 5.0.Z, 4.2.Z.

Unsupported Release Series

When a release series is no longer supported, it's your own responsibility to deal with bugs and security issues. We may provide backports of the fixes and publish them to git, however there will be no new versions released. If you are not comfortable maintaining your own versions, you should upgrade to a supported version.

Last updated on 2019-7-7
← Ruby on Rails Guides Guidelines
  • New Features
  • Bug Fixes
  • Security Issues
  • Severe Security Issues
  • Unsupported Release Series
Rails Setup 2019