From 91ab87cca83e0b43669b9299baaa531c12f2d9e9 Mon Sep 17 00:00:00 2001 From: KapilSachdev Date: Mon, 24 Aug 2020 00:42:55 +0530 Subject: [PATCH] fix(guides): Link maintenance policy to contributing guides [ci skip] --- guides/source/contributing_to_ruby_on_rails.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index f35e653a02..83bea08b73 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -677,6 +677,8 @@ $ git checkout 4-0-stable TIP: You may want to [put your Git branch name in your shell prompt](http://qugstart.com/blog/git-and-svn/add-colored-git-branch-name-to-your-shell-prompt/) to make it easier to remember which version of the code you're working with. +NOTE: Before working on older versions, please check the [maintenance policy](maintenance_policy.html). + #### Backporting Changes that are merged into master are intended for the next major release of Rails. Sometimes, it might be beneficial for your changes to propagate back to the maintenance releases for older stable branches. Generally, security fixes and bug fixes are good candidates for a backport, while new features and patches that introduce a change in behavior will not be accepted. When in doubt, it is best to consult a Rails team member before backporting your changes to avoid wasted effort.