Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Documented upgrading path for a major version#5155

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

Merged
weaverryan merged 7 commits intosymfony:2.3fromwouterj:prepare-major-version
May 25, 2015

Conversation

@wouterj
Copy link
Member

QA
Doc fix?no
New docs?yes
Applies toall
Fixed tickets#5059, partially#5111

I feel like there are lots of questions about this topic and nothing has officially been written about it yet. This PR is a first shot at documenting the steps you need to take.

I found this one of the hardest things to explain in an easy way. I hope others can improve it a bit :)

Todo

  • Add image of toolbar
  • Add result of PhpUnit bridge

@wouterjwouterjforce-pushed theprepare-major-version branch fromb968342 todac504aCompareApril 7, 2015 20:37
@wouterjwouterj changed the titleDocumented upgrading path for a major version[WIP] Documented upgrading path for a major versionApr 7, 2015
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

typo:still work, hile the new feature ->still work, while the new feature

@javiereguiluz
Copy link
Member

@wouterj nice work and very important articles. Thanks!

@wouterjwouterjforce-pushed theprepare-major-version branch 2 times, most recently fromc846723 to8c70f18CompareApril 9, 2015 08:32
@wouterj
Copy link
MemberAuthor

Thanks@javiereguiluz! I've applied your suggestions and added the missing screenshot.

@wouterjwouterj changed the title[WIP] Documented upgrading path for a major versionDocumented upgrading path for a major versionApr 9, 2015
@wouterjwouterjforce-pushed theprepare-major-version branch from8c70f18 tof3a130aCompareApril 9, 2015 09:18
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

2.8 will be the last minor version.

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

do you know if this always will be the case? Will the second last minor version always contain the deprecation triggers and is the last minor version always released together with the new major version?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

For now, I would not treat this as an absolute rule.

@wouterj
Copy link
MemberAuthor

Thanks everyone. I've now updated this PR

@xabbuh
Copy link
Member

We just need to find a consensus on whether or not to do the split (see#5186).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

should be safe...

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Hah, these are your own words 😉

@weaverryan
Copy link
Member

@wouterj I suggested some changes. I don't feel strongly, but my preference is to have an installand an upgrade section, mostly because upgrade isso important (install is actually less important, people will generally go elsewhere - e.g. symfony.com/download - to install) that I don't want to have to hide it under a "Install and Upgrade" section.

@wouterj
Copy link
MemberAuthor

Thanks@weaverryan. I've fixed them. I also think we should have a seperate upgrade section.

@wouterjwouterj added this to the2.7 milestoneMay 24, 2015
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Missing closing angle bracket here after the document name.

@weaverryan
Copy link
Member

GREAT work on this Wouter! I shouldn't be, but I can't tell you how excited I am to have these sections :). Thanks!

@weaverryanweaverryan merged commit604ccab intosymfony:2.3May 25, 2015
weaverryan added a commit that referenced this pull requestMay 25, 2015
This PR was merged into the 2.3 branch.Discussion----------Documented upgrading path for a major version| Q | A| --- | ---| Doc fix? | no| New docs? | yes| Applies to | all| Fixed tickets |#5059, partially#5111I feel like there are lots of questions about this topic and nothing has officially been written about it yet. This PR is a first shot at documenting the steps you need to take.I found this one of the hardest things to explain in an easy way. I hope others can improve it a bit :)Todo---* [x] Add image of toolbar* [x] Add result of PhpUnit bridgeCommits-------604ccab Fix formatting error31999db Fixes after review55fcee9 Applied comments99c5075 Fix typo300e8ab Added new recipe on upgrading a major version2b0aee3 Fix little title case mistake6a90c9b Created 'upgrade' cookbook section
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

2.7

Development

Successfully merging this pull request may close these issues.

6 participants

@wouterj@javiereguiluz@xabbuh@weaverryan@sstok@rvanlaak

[8]ページ先頭

©2009-2025 Movatter.jp