-
-
Notifications
You must be signed in to change notification settings - Fork 36
Add Roundup #13 #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Roundup #13 #90
Conversation
🚀 Deployed on https://deploy-pr-90--thephpfoundation.netlify.app |
@pronskiy I guess we can also add few words about PHP 8.2.6 and 8.1.19 (bug fix), And also 8.3.0alpha1 is already tagged. -- In Support section only Open Collective is listed, what do you think about GH Sponsors? |
Hi Roman and Sergey,
Thank you for this, and I'm just blown away how clever the ChatGPT response
is!
I was struggling a bit lately with time because my brother's wedding is
_today_, and was figuring out a lot of things here in the previous few
days. I should be available for the next one, but could you folks kindly
take care of the Issue 13 please?
Thank you 💜so much
…On Wed, Jun 7, 2023, 2:57 AM Sergey Panteleev ***@***.***> wrote:
@pronskiy <https://github.com/pronskiy> I guess we can also add few words
about PHP 8.2.6 and 8.1.19 (bug fix),
and/or 8.2.7, 8.1.20, 8.0.29 (security), if you plan to publish it after
June 8.
And also 8.3.0alpha1 is already tagged.
In Support section only Open Collective is listed, what do you think about
GH Sponsors?
—
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGEIIJSQN56MZA5KZYDBLXJ6OEVANCNFSM6AAAAAAY46MDKY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks! I've added PHP 8.2.6 and 8.1.19, the rest we'll mention in the next roundup. |
I'm not sure what is expected here. I've had a read through it at it appears to be accurate. One small nit with regard to my #[\Override] RFC:
The "potentially help static analysis tools" is a little misleading. The RFC explicitly includes that the attribute is actually checked by the engine itself, not just “potentially” and it also does not require the use of external static analysis tools. Quoting from the proposal (highlighting not in the original):
|
Co-authored-by: Sergey Panteleev <[email protected]>
Co-authored-by: Sergey Panteleev <[email protected]>
I did not hear back from @Ayesh yet, so here is an experimental Roundup draft composed mostly with ChatGPT and @Ayesh's script https://git.sr.ht/~ayesh/php-src-commit-formatter.
Here is the prompt I used:
Details
You'll be writing a blog post that overviews what the PHP core team has accomplished during the last month.
Next, I'm going to provide you with the format and instructions on how to do that.
In the curly braces I'm going to provide parts that needs to be replaced. You'll find instructions on replacement inside the curly braces.
Ask me questions that may help you.
PHP Foundation team (you'll need this later):
Sebastian Bergmann
Joe Watkins
Nils Adermann
Benjamin Eberlei
Josepha Haden
Roman Pronskiy
Nicolas Grekas
Sara Golemon
Nikita Popov
Matthew Weier O'Phinney
Derick Rethans
George Peter Banyard
Ilija Tovilo
Jakub Zelenka
Máté Kocsis
Arnaud Le Blanc
FORMAT:
Output as markdown.
Title:
PHP Core Roundup #{number of issue, see the list of previous posts here https://thephp.foundation/blog/tag/roundup/ and use +1 number from previous one}
Intro:
In the intro you need to make a catchy hook that sums up everything you have to say below. See some examples in the previous posts here https://thephp.foundation/blog/tag/roundup/.
RFC Updates:
Here is the list of RFCs you need to describe:
For each RFC from the list above, write a short block in the following format:
RFC {status – get it from the each RFC page in header section}: {RFC title} by {RFC authors list comma separated. If the RFC author is from the PHP Foundation team then add "💜" near his name. You can check the PHP Foundation team in the list above}
{Short summary of what the RFC is about. You can provide code examples if it helps. But keep it concise overall.}
Notable Mailing List Discussions
List:
For each discussion from the list above, write a short block in the following format:
{title = list item with link}
{Short summary of what the proposal is about and sentiment of the comments provided by other people in the each thread.}
Merged PRs and Commits
For the list of commits below, group them by the author and provide nested list in the format:
{list of commits from the original list each on a separate line starting with "- "}
The original list of commits:
run-tests.php
in GH-10892 by Ilija Tovilo 💜ext/pgsql
: pg_cancel_query internal update in 84c185c8ba by David CARLIERext/pgsql
: pg_trace allow to refine its trace mode via 2 new constants in 7ec8ae12c4 by David Carlierext/pgsql
: pg_lo_read addressing the todo. in GH-11159 by David CARLIERhttp_response_code
should warn if headers were already sent in GH-10744 by Calvin Buckleyext/pgsql
adding PGSQL_ERRORS_SQLSTATE constant support in f31d253849 by David CARLIERext/pgsql
: fix pg_trace test when trace mode is supported. in GH-11191 by David CARLIERphar_object.c
in GH-11202 by Ilija Tovilo 💜ZEND_NUM_ARGS()
in 80c8ca9c8f by George Peter Banyard 💜phar.php
during cross-compile can't be done in GH-11243 by Petermbfilter_cjk.c
in 245daedb41 by Alex Dowadext/session
: pass ini options to extra processes in tests in GH-11294 by Mikhail Galaninzend_shared_alloc_startup()
in GH-11306 by Niels Dosschezend_jit_stop_counter_handlers()
performance issues with protect_memory=1 in GH-11323 by Ilija Tovilo 💜@TimWolla, @saundefined, could you please help finish this up?