Skip to content
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

PHP 8 release announcement #350

Closed

Conversation

naruzl
Copy link
Contributor

@naruzl naruzl commented Nov 6, 2020

Implementation for PHP 8 release announcement https://externals.io/message/112026

@pronskiy
Copy link
Contributor

pronskiy commented Nov 11, 2020

@carusogabriel, @sgolemon, @cmb69 could you please help review the draft?

Should the page go under releases/8_0_0.php?

Work in progress:

Copy link
Contributor

@carusogabriel carusogabriel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Is there a typo on this image? Shouldn't it be:

-PHP 8 withot JIT
+PHP 8 without JIT

@cmb69
Copy link
Member

cmb69 commented Nov 14, 2020

Thank you for the great work! I'm generally in favor of this, because in my opinion, php.net would really profit from a modern looking representation of the PHP 8.0 relase, compared to what we did so far. I assume that some may not like the style, and/or that the page doesn't integrate into the general style of php.net (if there is even a general style), so it might be best to also send a mail to the internal webmaster ML.

Should the page go under releases/8_0_0.php?

I think for consistency and regarding that this info is useful for following revision releases, it should not. A link to the new page could be put on releases/8_0_x.php instead.

releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
@wol-soft
Copy link
Contributor

Is it intended that the Saner string to number comparisons is listed twice on the site?

@samdark
Copy link
Contributor

samdark commented Nov 18, 2020

@wol-soft no. @pronskiy that should be fixed.

releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
@flavioheleno
Copy link

flavioheleno commented Nov 19, 2020

Translation to PT-BR (release/8_0_x_pt_BR.php) available in https://gist.github.com/flavioheleno/206f630c1a88881fb17fb225e9415c8f
(cc @pronskiy & @carusogabriel)

releases/8_0_x.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
Copy link
Member

@saundefined saundefined left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some more :)

releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
releases/8_0_x_ru.php Outdated Show resolved Hide resolved
function release_language_chooser($currentlang) {
$LANGUAGES = array(
'en' => 'English',
'pt_BR' => 'Brazilian Portuguese',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Odd that 'pt_BR' gets a locale, but other languages are generalized. I appreciate that's probably a quick of Brazilian Portuguese, but if the criteria is about the default being spoken more in the colonies than the mother land, then let me tell you about American English. :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the same for the PHP manual; there was pt, later came pt_BR, and now only the latter is published.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just an extra info: there was an international agreement that reduced the differences between european portuguese and brazilian portuguese, with full transition ended by 2016 (source)

$_SERVER['BASE_PAGE'] = 'releases/8_0_x.php';
include_once __DIR__ . '/../include/prepend.inc';

if ($LANG !== 'en' && file_exists("8_0_x_$LANG.php")) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't trust $LANG to be sanitized by prepend.inc or whatever provided it.
Also, CWD shouldn't be assumed. This file should still render even if CWD is the root of the web checkout.

if (($LANG !== 'en') && file_exists(__DIR__ . '/8_0_x_' . basename($LANG) . '.php')) {
    mirror_redirect('/releases/8_0_x.php_' . urlencode($LANG) . '.php?lang=' . urlencode($LANG));
}

Here and elsewhere in these files.

Copy link
Contributor

@sgolemon sgolemon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To @cmb69's question; Yes. I think it's reasonable to get the page on the webserver ahead of time with the link not exposed yet. No problem with that. In fact, can switch it on this to make it automatic:

include __DIR__ . '/../include/version.inc';
if (!empty($GLOBALS['RELEASES'][8])) showTheLink();

As for the rest, I want anything that winds up in output (even headers) or file access escaped properly.

@samdark
Copy link
Contributor

samdark commented Nov 25, 2020

urlencode should be added to new translation pages as well.

@wol-soft
Copy link
Contributor

German translation updated in naruzl#5

@pronskiy
Copy link
Contributor

pronskiy commented Nov 25, 2020

@SjonHortensius sorry, but I had to drop Dutch translation, because Dutch is declared as inactive and I don't see a quick way to enable it in one place and keep inactive on the rest of the site.

@naruzl naruzl marked this pull request as ready for review November 25, 2020 11:42
@SjonHortensius
Copy link
Contributor

@pronskiy I understand - I should have checked that before I did the actual translation

@pronskiy
Copy link
Contributor

@sgolemon thanks for suggestions, changes have been applied.

@cmb69 @sgolemon do you think we can proceed with merge now?

Copy link
Contributor

@carusogabriel carusogabriel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The images/php8/jit.png image still has the without typo.

@@ -0,0 +1,797 @@
<?xml version="1.0" encoding="utf-8"?>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't understand this image. What these numbers say?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shows the relative performance impact of JIT compared to PHP 8 running without JIT. For example, running PHP-Parser with Function JIT is 2.11 times faster than running it on PHP 8 with JIT disabled. Does it make sense to you?

Copy link
Contributor

@carusogabriel carusogabriel Nov 25, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should add some captions as hint? It makes sense, but at first, someone might have this same question :)

include/layout.inc Outdated Show resolved Hide resolved
Co-authored-by: Gabriel Caruso <carusogabriel34@gmail.com>
Copy link
Contributor

@sgolemon sgolemon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sgolemon
Copy link
Contributor

I'm going to go ahead and merge this. We can still make edits, but it'll be nice to have it up on the site where we can see it.

@php-pulls
Copy link

Comment on behalf of pollita at php.net:

Pushed with a few of my own opinionated edits

@php-pulls php-pulls closed this Nov 25, 2020
@sgolemon
Copy link
Contributor

sgolemon commented Nov 25, 2020

https://www.php.net/releases/8.0 is rendering 'en' for me just fine, but I don't seem to be able to change my language, so a little more tweaking is prolly necessary.

Edit to add: My fault. Sigh.... ad13414

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.