Hi Everyone, I'm glad to see this coming up, this is something I've seen discussed a lot on and off the list.
It strikes me that asking an implementor to support multiple PSR versions is too much if we're just using composer versions. The only way I can imagine implementing something like that is by detecting the spec version and loading different versions of your implementation with your class loader. I really like Stefano's thinking. The namespace bit isn't my favorite but I understand why it could be important. - The Revision number matches the Semver package version, but it's doesn't > map exactly to the same concept. The most relevant part is obviously the > major number because minor and patch should not break compatibility, thus > releasing a new Revision will not be required. > What would distinguish a "minor" change from a "patch" change? Are you thinking a minor change would be errata and a patch would be typo fixes? Thanks, Korvin -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CANeXGWXti2DXW9VByMDZ2wtSNLJqAzP6tN9jsFvki17z6b%2BV7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
