Errata: Type additions

[navarr]

Errata for proposed PR to introduce new types in PSR-16 (simple cache)

Proposed versions are:

• v2.0.0 - Add Parameter Types (versions 2 of the library) simple-cache#25
• v3.0.0 - Add Parameter & Return Types (versions 3 of the library) simple-cache#24

[Jean85]

On hold until this passes the required CC vote.

[navarr]

@Crell Is it OK/appropriate to edit the PSR example code to match the interface as defined by the errata as I have done in 069fd7f?

Errata clarifications may only be added to the meta document, not to the spec itself, as items in their own section. The spec itself may only be minimally edited to point readers toward a relevant errata if appropriate.

https://www.php-fig.org/bylaws/psr-workflow/

[navarr]

@dragoonis: You're the editor of PSR-16, would you support this errata?

[Geolim4]

Hello @Jean85 any news about this ? When this MR will pass ?

[Jean85]

No vote has been called for the CC yet. We need @dragoonis to push it or someone else to take over.

[Crell]

Per the new bylaw updates, the CC can appoint a new Maintainer at its leisure. Or it can just make the updates on its own authority. We don't need Paul as he's clearly uninvolved anymore.

[Crell]

I think this is OK now.

[Crell]

I think we can take this to a CC vote now. Everything seems good to me. Thanks, @Geolim4!

[Geolim4]

I think we can take this to a CC vote now. Everything seems good to me. Thanks, @Geolim4!

Okay, nice. Poke me when you release the 3.0.0 so I can update my composer constraint asap.

Thanks again for your time boys.

[Geolim4]

Per the new bylaw updates, the CC can appoint a new Maintainer at its leisure. Or it can just make the updates on its own authority. We don't need Paul as he's clearly uninvolved anymore.

@Crell does Maintainer application is open to anyone or only to Fig member ?
If it is open to external people, I would propose myself to maintain this PSR on behalf of Phpfastcache project.

[Crell]

The Maintainer of a given artifact is appointed by the Core Committee by Approval Vote. Once a given artifact is created, the Maintainer may step down and name a replacement Maintainer at any time with Implicit Approval. If necessary, a Decision vote to appoint a new Maintainer may be held following a suitable nomination period.

Could be anyone. I... think that's slightly confusing as written (and I JUST wrote it, damnit, where are my reviewers at???), but I think if you apply via the list and no one else is interested, we just have an Approval vote on you. If someone else also steps forward, we have a Decision Vote to choose among you.

That doesn't block a vote on these changes, though. Right now the CC itself is the maintainer, which means we can just call an Approval vote like we did on the others.

[Geolim4]

@Crell @Jean85 when will the vote ends so I can plan an approximate date to update my dependencies. Thank you.

[Jean85]

@navarr I've added the \Throwable fix in #25 with php-fig/simple-cache@dd145de, should we add something here about it?

[navarr]

@Jean85 The symfony issue was specific to versions prior to 7.4 right? Are there any requirements from implementing libraries that come with this change?

I've currently got in my editor the diff:

- ### 8.1 Type additions
+ ### 8.1 Throwable
+ 
+ The 2.0 release of the `psr/simple-cache` package updates `Psr\SimpleCache\CacheException` to extend `Throwable`.
+ 
+ ### 8.2 Type additions

[Jean85]

Yes, the issue was only for PHP versions older than 7.4. Diff LGTM 👍 maybe just add a leading \ to Throwable to avoid confusion.

[Geolim4]

Hello,

Sorry I'm bumping the PR again but when will this PHP-8 upgrade will be released ?

It's been while now that the PHP community waits for this upgrade.

Thank again.

[navarr]

This is now up for a vote with the Core Committee: https://groups.google.com/g/php-fig/c/DJ8ysB1JV4Y

[Geolim4]

Hello, I'm bumping again but when will this v3 of the library will be released ?
The vote seems to take so long now :(

[navarr]

@Geolim4 indeed! We've passed quorum and have >2/3 of the entire committee voting yes. Voting officially ends tomorrow and then after that it can be merged.

So, I would expect this to get merged tomorrow

[vdelau]

The vote is concluded and the proposal is accepted (https://groups.google.com/g/php-fig/c/DJ8ysB1JV4Y/m/a9hNoIG5AwAJ)

[ADmad]

@Crell does Maintainer application is open to anyone or only to Fig member ?
If it is open to external people, I would propose myself to maintain this PSR on behalf of Phpfastcache project.

Can we get the ball rolling on making @Geolim4 a maintainer for the Simple Cache PSR? Clearly he's the one most interested it in keeping it up to date and has expressed his interest in helping maintain it. The PHP community would surely appreciate a more faster pace of handling updates than what FIG currently has to offer.

[Geolim4]

@Crell does Maintainer application is open to anyone or only to Fig member ?
If it is open to external people, I would propose myself to maintain this PSR on behalf of Phpfastcache project.

Can we get the ball rolling on making @Geolim4 a maintainer for the Simple Cache PSR? Clearly he's the one most interested it in keeping it up to date and has expressed his interest in helping maintain it. The PHP community would surely appreciate a more faster pace of handling updates than what FIG currently has to offer.

Actually I'm one of the "rare" libraries that implements (and support) PSR-6 and PSR-16 (via adapter) and to release the next major release PHP-8 compatible only I needed this PSR to be updated, but I'm really surprised to be the only one concerned by this update, I was expecting more people involved.

[ADmad]

@Geolim4 The change for adding types really didn't need much of involvement from the community. Just the FIG team needed regularly nudges to move the process along, which thankfully we had you doing 🙂.