What's New in Rails 4.1.4 Latest Version with bug Fixes and Features?

We all knows that, Rails New Version 4.1.4 has been released, and lots of bug fixes and some new features added.

gem 'rails', '~> 4.1.4'

Time between release candidate and actual release


Check the rails-core mailing list and the GitHub issue list for regressions in the RC.
If any regressions are found, fix the regressions and repeat the release candidate process. We will not release the final until 72 hours after the last release candidate has been pushed. This means that if users find regressions, the scheduled release date must be postponed.
When you fix the regressions, do not create a new branch. Fix them on the stable branch, then cherry pick the commit to your release branch. No other commits should be added to the release branch besides regression fixing commits.

Day of release

Many of these steps are the same as for the release candidate, so if you need more explanation on a particular step, see the RC steps.
Today, do this stuff in this order:
  • Apply security patches to the release branch
  • Update CHANGELOG with security fixes.
  • Update RAILS_VERSION to remove the rc
  • Build and test the gem
  • Release the gems
  • If releasing a new stable version:
    • Trigger stable docs generation (see below)
    • Update the version in the home page
  • Email security lists
  • Email general announcement lists

Emailing the Rails security announce list

Email the security announce list once for each vulnerability fixed.
You can do this, or ask the security team to do it.
Email the security reports to:
  • rubyonrails-security@googlegroups.com
  • oss-security@lists.openwall.com
Be sure to note the security fixes in your announcement along with CVE numbers and links to each patch. Some people may not be able to upgrade right away, so we need to give them the security fixes in patch form.
  • Blog announcements
  • Twitter announcements
  • Merge the release branch to the stable branch.
  • Drink beer (or other cocktail)

Misc

Fixing the CI

There are two simple steps for fixing the CI:
  1. Identify the problem
  2. Fix it
Repeat these steps until the CI is green.

Comments

Post a Comment