Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
Added a new article about using/installing unstable Symfony versions#5186
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| In this article you'll learn how to install and use new Symfony versions before | ||
| they are released as stable versions. | ||
| Creating a New Project Based on an Inestable 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.
Unstable should be used imo
nice trick about router.request_context.base_url 👍 |
@javiereguiluz configuring |
| // ... | ||
| "symfony/symfony" : "2.7.*" | ||
| }, | ||
| "minimum-stability": "dev" |
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.
or better"symfony/symfony" : "2.7.*@dev" to install only Symfony dev version, and not your whole ecosystem.
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.
You are right. I've simplified everything to not use theminimum-stability option. Thanks!
don't forget to add the old URL of the upgrading article in the redirection map |
| $ composer update | ||
| If you prefer to test a Symfony beta version, replace the ``"2.7.*@dev"`` constraint | ||
| by ``"2.7.*@beta1"`` (or any other beta number). |
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.
you cannot put a beta number in the stability flag. It is either2.7.0-beta1 (i.e. explicit version constraint for a single version, which automatically adds a stability flag for thet package given it is a root requirement involving a beta version), or2.7.*@beta (getting the most recent version of Symfony being at least in beta stability)
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.
Thanks for the explanation. I've reworded as:
If you prefer to test a Symfony beta version, replace the ``"2.7.*@dev"`` constraintby ``"2.7.0-beta1"`` to install a specific beta number or ``2.7.*@beta`` to getthe most recent beta version.I propose to instead of mixing upgrading and installing, just have a section about installing (created by this PR) and one about upgrading (created by#5155). |
I've added all the suggestions made by reviewers. Regarding the proposal made by@wouterj, I don't agree with it because I think installing and upgrading Symfony are closely related topics. Moreover, splitting this small section would produce two very tiny sections. |
Can we considered this PR finished? |
We just need to find a consensus on whether or not to do the split (see#5155). |
| @@ -0,0 +1,82 @@ | |||
| How to Install and Use an Unstable 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.
I'd change this - I thought "unstable" at first meant an "old, unsupported" version (e.g. 2.4)". I know that's not logical, but that's what I thought :). How about:
How to Install or Upgrade to the Latest, Unreleased Symfony Version
FWIW - my vote is to keep these as 2 sections:#5155 (comment) |
| Symfony releases two new minor versions (2.5, 2.6, 2.7, etc.) per year, one in | ||
| May and one in November (:doc:`see releases detail </contributing/community/releases>`). | ||
| Testing the new Symfony versions in your projects as soon as possible is important | ||
| to ensure that they will keep working after upgrading to the new 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.
I'm not sure this paragraph adds enough value
| Instead of creating a new empty project, in this section you'll update an existing | ||
| Symfony application to an unstable framework version. Suppose again that Symfony | ||
| 2.7 version hasn't been released yet and you want to test it in your project. |
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.
How about just:
Suppose again that Symfony 2.7 hasn't been released yet and you want to upgrade an existingapplication to test that your project works with it.
621e2ab to1378ec9CompareI've just fixed the last issues of this PR. The only remaining issue is the split suggested by Ryan. I don't mind doing that split, but I don't like doing that in this PR because it's already complex enough. Could we reorder the contents in a further separate PR? Thanks. |
I'm sorry, but why is the split too complex? You added one article in this PR and all you need to do is remove the changes related to the Merging this PR in the current state makes things really weird, as the |
…fony versions (javiereguiluz)This PR was merged into the 2.3 branch.Discussion----------Added a new article about using/installing unstable Symfony versions| Q | A| ------------- | ---| Doc fix? | no| New docs? | yes| Applies to | all| Fixed tickets | -In addition to the new article, I propose to move the existing `upgrading.rst` article to the new "Installing and Upgrading" section. New articles related to this topic will be added soon. I plan to add at least two articles: * How to install Symfony with Composer (this will allow us to simplify installation instructions across the documentation and just recommend to use the installer). * How to install Symfony in a Subdirectory (it's not uncommon to have to execute Symfony apps in URLs such as example.com/my-symfony-app/ It's not hard, but at least you have to configure the `router.request_context.base_url` config option, which I think is documented nowhere).Commits-------8e8fad2 Removed some wrong labels1378ec9 Added a note about the Symfony Upgrading Guide224c380 Fixed a lot of issues pointed by Ryand5f3d82 Minor improvement in a command038caa5 Fixed minor issuesbae8043 Fixed the beta version constraintsa9fee2f Fixed a link to an internal documentcaff8d2 Minor rewordinge1f621e Added a new entry in the redirection_map724c17f Simplified instructions6d6303c Fixed a minor error in some index file719e52c Added the missing file extension2722933 Fixed articles linksdf22b75 Fixed typo: "inestable" -> "unstable"402f5d4 Added a new articule about using/installing inestable Symfony versions
…uments in its own sectionSo, this is not really removing anything - it's just that this article was "moved" originally,in#5186, but then later on a rebase, it appeared that this upgrading.rst was "added".The result is the intention of the#5186 PR: to add a new "install" section with*just* the new "unstable" article.
Hey guys! I merged this in, and got all the "moving" things cleared up at sha:875f4ee If you see any issues, let me know! Thanks! |
In addition to the new article, I propose to move the existing
upgrading.rstarticle to the new "Installing and Upgrading" section. New articles related to this topic will be added soon. I plan to add at least two articles:router.request_context.base_urlconfig option, which I think is documented nowhere).