Adds the Rails maintenance policy to the Guides #12171
Conversation
|
ping @steveklabnik |
|
Please add |
| Maintenance policy for Ruby on Rails | ||
| ==================================== | ||
|
|
||
| Since the most recent patch releases there has been some confusion about what versions of Ruby on Rails are currently supported, and when people can expect new versions. Our maintenance policy is as follows. |
There was a problem hiding this comment.
May you use 80 chars width for lines.
|
Updated the PR with wrapped lines and |
|
👍 |
|
|
||
| You should also be aware that Ruby 1.8 reached End of Life in June 2013, no | ||
| further Ruby security releases will be provided. If your application is only | ||
| compatible Ruby 1.8 you should upgrade accordingly. |
There was a problem hiding this comment.
This isn't needed because we don't support 1.8 at all any more.
|
I wish I'd thought of this. @fxn? |
|
I removed the note about Ruby 1.8, would you like me to squash the commits? |
|
Yes, please. |
|
OK, done. |
|
I don't think this belongs to rails guides. This is an intitutional On Monday, September 9, 2013, Steve Klabnik wrote:
Rafael Mendonça França |
|
I think it's fairly logical to find it in the guides, especially as that's where you find the release notes for major versions… |
|
Also, perhaps it's an inditement of the current state of the Rails website, but I (at least) almost never go looking for up-to-date information about Rails on the Rails website (aside from the blog). |
|
I think that we should better add this to the contribution guideline just with a link pointing to the article. |
|
The maintenance policy isn't important just to contributors, it affects every person developing anything on top of Rails… Plus it has extremely important security implications for everyone who works with Rails. |
|
@matiaskorhonen : Uh, good point! |
|
Should 'Bug fixes' go to 3.2.x too? |
|
@arthurnn see http://weblog.rubyonrails.org/2013/7/23/Rails-3-2-14-has-been-released/
|
|
Hey I am 👍 on adding this to the guides. Will check the details of the PR later today. |
|
Yeah, I have been browsing the website and don't quite see this page there. The home is kind of in a higher/broader level in my view. The other extreme would be a file in the root directory of the project or something, but as has been already said, the maintenance policy is something that interests to different kind of people and for some this wouldn't be a good way of communicating it. And definitely as a blog post cannot fly, we need it documented in the project. A guide seems like a good place to me, since they already deviate a little bit from the pure documentation of topics with the release notes. So in principle my vote is positive. Would like to suggest two things:
|
|
Make sense. Thank you for taking care of this one |
|
I added a separate section for the maintenance policy, added an entry to the CHANGELOG, and squashed everything into a single commit. |
|
Awesome, thanks for working on this. |
…-to-guides Adds the Rails maintenance policy to the Guides
I propose that we add the Rails maintenance policy to the Ruby on Rails Guides.
At the moment if you want to check the maintenance policy you have to find the blog post about it way from back in February and it doesn't seem to have been updated after Rails 4 was released.
Ideally Rails Guides should be the canonical source for the maintenance policy (and I think there would be a better chance of it staying up-to-date from release to release)…
I've done my best to update the maintenance policy to the current state from the blog post from February and I'm fairly certain that it reflects reality, but someone more knowledgeable should check it to be sure.