On Thu, Jun 18, 2020 at 3:16 PM Larry Garfield <la...@garfieldtech.com> wrote:
> On Thu, Jun 18, 2020, at 2:05 PM, Matthew Weier O'Phinney wrote: > > > > Also: Matthew, why the first release would be 2.0? Can't we declare it > a 1.1 to make the transition smoother, as suggested by the bylaw? > > > > I got confused on that by Larry's blogpost, but you're absolutely > correct. > > Per both bylaw and blog post, both 1.1 and 2.0 are valid approaches > depending on the details. In this case it would mainly depend on whether > we consider changing from docblock "string" to type definition "string", > which does technically now prevent stringable objects when they probably > worked before, an API break. > > That's a case-by-case question we get to sort out. I agree with MWOP that > in this case no one has any damned business using a stringable object here > to begin with, so it's not really a BC break in any meaningful sense. So, > either way could work. > > MWOP: remember to also make a PR for the PSR itself to note the change in > errata. I think the PSR-13 PR had something you could steal from. > Done: - https://github.com/php-fig/fig-standards/pull/1215 -- Matthew Weier O'Phinney mweierophin...@gmail.com https://mwop.net/ he/him -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAJp_myUPZ-1uKZhDDS4v8%2BeV97DBgtfoY9O0bB9QQPffTSOrBg%40mail.gmail.com.
