-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the docs ready for 2.4 #2690
Conversation
> **Note** | ||
> Unless you're documenting a feature that's new to a specific version of Symfony | ||
> (e.g. Symfony 2.2), all pull requests must be based off of the **2.2** | ||
> branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backported to 2.2
|
||
.. tip:: | ||
|
||
For an exact version, replace `2.2.0` with the latest Symfony version | ||
(e.g. 2.2.1). For details, see the `Symfony Installation Page`_ | ||
For an exact version, replace ``2.3.*`` with the latest Symfony version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"with the latest Symfony version" is a little bit confusing as 2.3.*
already installs the latest version. I would go for "replace 2.3.*
with the particular Symfony version".
@weaverryan done, much less conflicts than I thought :) |
Hey Wouter! According to our new rules, we should not remove these until 2.2 actually reaches its end of life. I think I'd like to follow those rules so we can keep our release process very simple. I've basically cherry-picked your README change at sha: 788292b. Thanks! |
2.2 will be deprecated when 2.4 is released. what about leaving this open and use it in november this year to remove all 2.2 stuff from the docs? |
Things to do when 2.4 is released:
book/installation
,components/using_components
andquick_tour/the_big_picture
)I'll rebase it when #2688 is merged