Agreeing with Woody. The implementation of the PSR should be treated as any other composer package, therefor using semver. This practice is familiar with all developers without needing to know any details about the PSR process. The PSR numbering should stay internal just for the ease of discussion inside the PHP-FIG community.
> On 12 Apr 2017, at 04:44, Adrien Crivelli <[email protected]> wrote: > > Couldn't agree more with Woody Gilk. > > PSR numbering may, or may not, be a nice things to organize the process, but > it should not intrude into code. Code should be upgraded using semver major > versions, as is expected for all composer packages. > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/1e576ddf-91fb-40c4-8111-90915eb67157%40googlegroups.com > > <https://groups.google.com/d/msgid/php-fig/1e576ddf-91fb-40c4-8111-90915eb67157%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/91932245-7A7D-49C0-8188-27F13471E5F2%40gmail.com. For more options, visit https://groups.google.com/d/optout.
