For interoperability and upgrade purposes, it would greatly appreciated to not change the namespace of the package. All those concerns can be easily handled with a new branch on each package imho. The package are focused on a topic (psr/log), not on a PSR number.
And maybe it's stupid, but, why should name those branches 2.0? Wouldn't it be easier and less confusing to have branches that stick to the PHP versions they are compatible with? Or maybe use aliases? On Tuesday, April 11, 2017 at 10:19:08 PM UTC+2, Larry Garfield wrote: > > Hello, peoples. In response to some recent off-list discussion (at > conferences and elsewhere), I offer this brief survey about how we > should namespace interface PSRs once we start producing "updated" > versions (eg, PHP 7-ified versions) of existing specs. The survey > itself has more details, and should take under a minute to complete. > Please do so! > > > https://docs.google.com/forms/d/e/1FAIpQLSc8VJySoz_3koQThe057zYhzSkmOvOAgO0pEmenwr1Biu6JEA/viewform > > > This is a non-binding information gathering tool only to kick off a > discussion, not to end one. Feel free to discuss more in this thread. > I'll leave the survey open for 2 weeks or until people stop responding > to it. :-) > > All are welcome and encouraged to respond, even if you're not a Core > Committee member or Project Rep. > > --Larry Garfield > > -- 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/dec622fc-f986-4eef-ae6c-e32b08a76574%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
