Conversation
mykiwi
commented
Jun 3, 2013
| Q | A |
|---|---|
| Doc fix? | yes |
| New docs? | no |
| Applies to | 2.3+ |
book/installation.rst
Outdated
There was a problem hiding this comment.
shouldn't 2.2.1 be replaced, too?
There was a problem hiding this comment.
I don't know. Should I write 2.3.1 (or something else)?
There was a problem hiding this comment.
maybe just remove the complete e,g. 2.2.1 part. We need to update that every time a new version is released
There was a problem hiding this comment.
I'm not sure. 2.3.1 was a bit confusing as 2.3.0 already is the latest version. Maybe 2.3.0 is sufficient if we just use 2.3 in the install command.
EDIT: didn't see WouterJ's reply when posting this. Probably omitting this completely really was the best solution.
|
|
|
and |
|
In |
|
Well, I think you should remove the branch versions on line 29 and just have: multiple branches, corresponding to the different versions of Symfony itself. |
|
Hey Roman! Thanks for this update - it's very well done! I've merged this in with minor tweaks at sha: 297af3e. Specifically, the Thanks! |
…e with the docu... (xabbuh) This PR was submitted for the master branch but it was merged into the 2.5 branch instead (closes #3882). Discussion ---------- change version numbers in installation notes to be in line with the docu... ...mented Symfony version | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | 2.5 | Fixed tickets | This PR updates the version constraints in the installation instructions as described [here](http://symfony.com/doc/current/contributing/documentation/overview.html#when-a-new-branch-is-created-for-a-release): > Change all version and master references to the correct version (e.g. 2.3). For example, in installation chapters, we reference the version you should use for installation. As an example, see the changes made in PR #2688. Commits ------- f77392a change version numbers in installation notes to be in line with the documented Symfony version