Good morning, all!
This is a friendly reminder from your RMs that the PHP 8.3 feature
freeze is in ~4 weeks on July 18th [1]. Alpha1 is already out and Alpha2
is scheduled this Thursday.
All new features and RFCs need to be discussed with voting polls closed
on or before July 18th for inclus
PHP 8.3 release management
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
I had volunteered in a previous cycle but, sadly, lost in the voting
round. That said, I'm still eager to be more heavily involved and up for
the challenge (both for the immediate process and for any long-term
support beyond the dates listed in the existing todo.
I've been working with PHP in
I'm in support of such a feature, but would strongly advocate for an
additional parameter to flag whether or not to include the trailing `=`
pad. The trailing pad is optional according to RFC 4648, so I think
leaving it off by default would be the ideal use case, but an optional
`include_paddin
I'm not sure I'm a fan of the PR as it stands, but the idea of
encrypting session data - definitely.
When sessions are stored on disk, that data is plainly visible by anyone
(or any process) with read access to that disk. If they're cached
instead in a DB or an in-memory system like Memcached,
Best of luck to all of the volunteers in this election!
To add some color about why I threw my hat in the ring (and save you the
trouble of trying to find the earlier thread):
I've been using PHP since the days of version 4 and our older/clunkier
method of OO programming. I've bounced around
I'm new to this mailing list as I'd previously (and very mistakenly)
assumed it was meant for existing contributors. So I've always consumed
conversations via web-based aggregators rather than directly.
My mistake.
That being said, I am very interested in being a part of this release.
I've be
