Skip to content

Instantly share code, notes, and snippets.

@weaverryan

weaverryan/README.md

Created July 30, 2015 16:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save weaverryan/b2ed3b52306d8b5eb4ef to your computer and use it in GitHub Desktop.
Save weaverryan/b2ed3b52306d8b5eb4ef to your computer and use it in GitHub Desktop.
Download ZIP
Symfony Core Meeting Summary July 30th, 2015
Raw
README.md

Deprecation Policy

Original conversation: symfony/symfony-docs#5413 (comment)

  • We agreed to trigger deprecation warnings immediately when something is deprecated, rather than waiting until a later version to "catch-up"
  • nicolas-greaks will open a small docs PR to mention how interface deprecation triggers work, since they - at the very least - befuddled weaverryan

PSR-7 Plan

Summary: Should we implement PSR-7 in HttpFoundation? What are the problems we want to solve

  • PSR-7 will be used primarily for middlewares. So, if the PSR-7 bridge works perfectly, is there a need to make HttpFoundation implement PSR-7?

  • A vote concluded to not convert HttpFoundation to PSR-7. But instead to make HttpFoundation look as much like PSR-7 as possible (in part, by moving mutable pieces out of HttpFoundation).

  • We also need to make any changes to make the PSR-7 bridge work perfectly. I believe there are still problems with large streams.

  • Individual components - e.g. Debug - will be made to support HttpFoundation and PSR-7. nicolas-grekas will start with Debug and also open an issue that tracks which components have support.

  • Per the vote, HttpKernel will be the only component that is not given PSR-7 support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment