# Skip 7.3.0RC6? - Thread: https://externals.io/message/103376 - Original archive: https://news-web.php.net/php.internals/103376 - Started by Sara Golemon on 2018-10-24T15:03:17+00:00 - Messages: 11 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #103376 — Sara Golemon — 2018-10-24T15:03:17+00:00 URL: https://externals.io/message/103376#103376 I've been thinking about this since we added the fourth alpha and pushed the schedule down, but thinking about the EOL of 7.0 on Dec 3rd, I'm wondering if it'd be worth skipping RC6 in order to GA 7.3.0 on Nov 22 (previously scheduled date) slightly ahead of the Dec 3 deadline. Obviously doing so would be contingent on the build looking stable as of RC5, and primarily the call of cmb and stas, but I wanted to get others' thoughts. -Sara --- ## #103377 — Christoph M. Becker — 2018-10-24T17:37:57+00:00 URL: https://externals.io/message/103376#103377 · In reply to: #103376 > I've been thinking about this since we added the fourth alpha and > pushed the schedule down, but thinking about the EOL of 7.0 on Dec > 3rd, I'm wondering if it'd be worth skipping RC6 in order to GA 7.3.0 > on Nov 22 (previously scheduled date) slightly ahead of the Dec 3 > deadline. Obviously doing so would be contingent on the build looking > stable as of RC5, and primarily the call of cmb and stas, but I wanted > to get others' thoughts. I've thought about this as well, but given that some widely used PECL extensions are not ready for PHP 7.3 yet (for instance, yaml[1], mailparse[2] and uopz[3]) (Remi may have more to say on this), it might be better to still have two additional RCs (RC4 has been tagged yesterday). Furthermore, timelib has only recently been upgraded to 2018.01RC1[4], and I think it may need some time to be stable. [1] [2] [3] [4] -- Christoph M. Becker --- ## #103378 — Sara Golemon — 2018-10-24T18:06:44+00:00 URL: https://externals.io/message/103376#103378 · In reply to: #103377 > I've thought about this as well, but given that some widely used PECL > extensions are not ready for PHP 7.3 yet (for instance, yaml[1], > mailparse[2] and uopz[3]) (Remi may have more to say on this), it might > be better to still have two additional RCs (RC4 has been tagged > yesterday). Furthermore, timelib has only recently been upgraded to > 2018.01RC1[4], and I think it may need some time to be stable. > That puts done to that topic then. Full RC cycle it is. I've been getting use out of ext/yaml, I'll take a look at addressing its 7.3 compat. -Sara --- ## #103379 — Derick Rethans — 2018-10-24T18:12:20+00:00 URL: https://externals.io/message/103376#103379 · In reply to: #103377 > > > > […] > > I've thought about this as well, but given that some widely used PECL > extensions are not ready for PHP 7.3 yet (for instance, yaml[1], > mailparse[2] and uopz[3]) (Remi may have more to say on this), it might > be better to still have two additional RCs (RC4 has been tagged > yesterday). Furthermore, timelib has only recently been upgraded to > 2018.01RC1[4], and I think it may need some time to be stable. > > [1] > [2] > [3] > [4] timelib should be considered stable, the last RC was just a data update. The commit ([4]) however, is unrelated to timelib? cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Like Xdebug? Consider a donation: https://xdebug.org/donate.php, or become my Patron: https://www.patreon.com/derickr twitter: @derickr and @xdebug --- ## #103380 — Christoph M. Becker — 2018-10-24T21:36:44+00:00 URL: https://externals.io/message/103376#103380 · In reply to: #103379 > > > timelib should be considered stable, the last RC was just a data update. Great! There may have to be some adjustments made to other extensions, see . > The commit ([4]) however, is unrelated to timelib? Sorry, this should have been . -- Christoph M. Becker --- ## #103381 — Jan Ehrhardt — 2018-10-25T04:02:31+00:00 URL: https://externals.io/message/103376#103381 · In reply to: #103377 "Christoph M. Becker" in php.internals (Wed, 24 Oct 2018 19:37:57 +0200): >I've thought about this as well, but given that some widely used PECL >extensions are not ready for PHP 7.3 yet (for instance, yaml[1], >mailparse[2] and uopz[3]) (Remi may have more to say on this), it might >be better to still have two additional RCs (RC4 has been tagged >yesterday). Additional extensions that are not ready for PHP 7.2 yet: - wincache - pthreads https://github.com/krakjoe/pthreads/issues/889#issuecomment-412330976 - request https://github.com/pmjones/ext-request/pull/14 - msgpack https://github.com/msgpack/msgpack-php/pull/124 -- Jan --- ## #103382 — Jan Ehrhardt — 2018-10-25T04:09:51+00:00 URL: https://externals.io/message/103376#103382 · In reply to: #103381 Jan Ehrhardt in php.internals (Thu, 25 Oct 2018 06:02:31 +0200): >Additional extensions that are not ready for PHP 7.2 yet: 7.3 --- ## #103383 — Remi Collet — 2018-10-25T05:32:00+00:00 URL: https://externals.io/message/103376#103383 · In reply to: #103377 Le 24/10/2018 à 19:37, Christoph M. Becker a écrit : > I've thought about this as well, but given that some widely used PECL > extensions are not ready for PHP 7.3 yet (for instance, yaml[1], > mailparse[2] and uopz[3]) (Remi may have more to say on this) I track extensions' status on https://blog.remirepo.net/post/2018/07/02/PHP-extensions-status-with-upcoming-PHP-7.3 91 are OK 31 are WIP (fixed upstream or PR waiting review) 12 are KO ev and zmq could be other used ones (for zmq PR open to fix the build, but still segfault in test suite) Remi --- ## #103384 — Jan Ehrhardt — 2018-10-25T06:59:16+00:00 URL: https://externals.io/message/103376#103384 · In reply to: #103383 Remi Collet in php.internals (Thu, 25 Oct 2018 07:32:00 +0200): >https://blog.remirepo.net/post/2018/07/02/PHP-extensions-status-with-upcoming-PHP-7.3 You can move v8js to work-in-progress. There is a 7.2+ branch: https://github.com/phpv8/v8js/issues/374#issuecomment-421262169 The Appveyor builds pass all applicable tests on Windows: https://ci.appveyor.com/project/Jan-E/v8js-rx24a/build/1.0.58 -- Jan --- ## #103412 — Julien Pauli — 2018-10-31T12:25:19+00:00 URL: https://externals.io/message/103376#103412 · In reply to: #103384 > Remi Collet in php.internals (Thu, 25 Oct 2018 07:32:00 +0200): > > […] > https://blog.remirepo.net/post/2018/07/02/PHP-extensions-status-with-upcoming-PHP-7.3 > > You can move v8js to work-in-progress. There is a 7.2+ branch: > https://github.com/phpv8/v8js/issues/374#issuecomment-421262169 > > The Appveyor builds pass all applicable tests on Windows: > https://ci.appveyor.com/project/Jan-E/v8js-rx24a/build/1.0.58 > -- > Jan > > -- > > I dont remember the status here, but , those extensions are not built-in right ? It seems to me like we are waiting for the world to upgrade its code, to release our next release. Have we always done that before ? What I remember, is that we wait for bundled extensions (those are the ones shipped with the PHP source code) to be compatible, but not for the all world's extension. Just asking :-) Julien.Pauli --- ## #103413 — Christoph M. Becker — 2018-10-31T13:10:10+00:00 URL: https://externals.io/message/103376#103413 · In reply to: #103412 > > > > […] > > I dont remember the status here, but , those extensions are not built-in > right ? Yes. > It seems to me like we are waiting for the world to upgrade its code, to > release our next release. > Have we always done that before ? > > What I remember, is that we wait for bundled extensions (those are the ones > shipped with the PHP source code) to be compatible, but not for the all > world's extension. Well, it's not that we wait until all external extensions are compatible, but we rather give them two more weeks to catch up – or, even rather, we don't ship GA earlier than scheduled as of 2018-07-11. -- Christoph M. Becker