Skip to content
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

Fix upgrade guide #21314

Merged
merged 1 commit into from Jan 28, 2017
Merged

Fix upgrade guide #21314

merged 1 commit into from Jan 28, 2017

Conversation

Jean85
Copy link
Contributor

@Jean85 Jean85 commented Jan 17, 2017

Q A
Branch? 2.7
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
License MIT

This merges back the UPGRADE-3.0.md guide from master back up to 2.7. There were a lot of missing parts and a few duplications. I fear that also the other guides have the same issues.

@Jean85 Jean85 changed the base branch from master to 2.7 January 17, 2017 00:37
@xabbuh
Copy link
Member

xabbuh commented Jan 17, 2017

Did you make sure that the missing parts just aren't things that were not deprecated in 2.7, but were only deprecated in 2.8?

@Jean85
Copy link
Contributor Author

Jean85 commented Jan 17, 2017

Should't that be the same? Also, a big missing part was the one about the Form deprecations, that I'm sure are from before 2.8.

Anyway, I'll double check that...

together with the `Valid` constraint instead.

* Type names were removed. Instead of referencing types by name, you must
reference them by their fully-qualified class name (FQCN) instead:
Copy link
Member

Choose a reason for hiding this comment

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

That's wrong. All these Form changes are part of Symfony 2.8, so they have nothing to do in the UPGRADE file in the 2.7 branch

@@ -1,6 +1,35 @@
UPGRADE FROM 2.x to 3.0
Copy link
Member

Choose a reason for hiding this comment

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

does it even make sense to have this title?
I mean: we do not support direct upgrade from 2.x to 3.0, when x < 8.

@Jean85 Jean85 changed the base branch from 2.7 to 2.8 January 17, 2017 09:14
@Jean85
Copy link
Contributor Author

Jean85 commented Jan 17, 2017

Ok I've rechecked everything.

I've changed the base branch to 2.8, and leaved only the changes that where really missing: the Monolog Bridge

* `Symfony\Bridge\Monolog\Logger::err()` was removed. Use `error()` which is PSR-3 compatible.
* `Symfony\Bridge\Monolog\Logger::warn()` was removed. Use `warning()` which is PSR-3 compatible.

* Removed the feature that allowed finding deep items in `ParameterBag::get()`.
Copy link
Member

Choose a reason for hiding this comment

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

this has nothing to do with the monolog bridge. you copy/pasted the changes of HttpFoundation below

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Merge screwup, sorry. Removed.

@nicolas-grekas nicolas-grekas added this to the 2.8 milestone Jan 24, 2017
@nicolas-grekas
Copy link
Member

👍

* `Symfony\Bridge\Monolog\Logger::emerg()` was removed. Use `emergency()` which is PSR-3 compatible.
* `Symfony\Bridge\Monolog\Logger::crit()` was removed. Use `critical()` which is PSR-3 compatible.
* `Symfony\Bridge\Monolog\Logger::err()` was removed. Use `error()` which is PSR-3 compatible.
* `Symfony\Bridge\Monolog\Logger::warn()` was removed. Use `warning()` which is PSR-3 compatible.
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should I change the base branch to 2.7 then?

Copy link
Member

Choose a reason for hiding this comment

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

That would be great. Otherwise we can do that while merging. But could you update the PR description please?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done and done, I've completely rewritten this branch to avoid a big mess.

@xabbuh xabbuh modified the milestones: 2.7, 2.8 Jan 27, 2017
@Jean85 Jean85 changed the base branch from 2.8 to 2.7 January 27, 2017 14:33
@fabpot
Copy link
Member

fabpot commented Jan 28, 2017

Thank you @Jean85.

@fabpot fabpot merged commit bd0c206 into symfony:2.7 Jan 28, 2017
fabpot added a commit that referenced this pull request Jan 28, 2017
This PR was merged into the 2.7 branch.

Discussion
----------

Fix upgrade guide

| Q             | A
| ------------- | ---
| Branch?       | 2.7
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| License       | MIT

This merges back the `UPGRADE-3.0.md` guide from master back up to 2.7. There were a lot of missing parts and a few duplications. I fear that also the other guides have the same issues.

Commits
-------

bd0c206 Add missing pieces in the upgrade guide to 3.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants