Right now we have this cyclus:
Week 1: 7.3.x RC1
Week 2: 7.4.x RC1
Week 3: 7.3.x Release, maybe 7.2.x Release
Week 4: 7.4.x Release
Week 5: 7.3.x+1 RC1
etc etc
Wouldn't it be better to sync our watches and release new versions of
PHP 7.4, 7.3 and possibly 7.2 at the same date, every 4 weeks?
This can be done by delaying the 7.3 and 7.2 release cycles with one
week. Proposal:
- Tag PHP 7.3.14RC1 on Tuesday Jan 7, Release on Thursday Jan 9
- Tag PHP 7.3.14 on Tuesday Jan 21, Release on Thursday Jan 23
- Tag PHP 7.2.27 (if any) on Jan 21, Release on Jan 23
Small changes would be needed to
https://www.php.net/supported-versions.php
Let us give the 7.3 RMs a New Years Eve
Jan Ehrhardt in php.internals (Tue, 10 Dec 2019 06:45:56 +0100):
Let us give the 7.3 RMs a New Years Eve
Let us give the 7.3 RMs a New Year's Eve without obligations.
Jan
Right now we have this cyclus:
Week 1: 7.3.x RC1
Week 2: 7.4.x RC1
Week 3: 7.3.x Release, maybe 7.2.x Release
Week 4: 7.4.x Release
Week 5: 7.3.x+1 RC1
etc etcWouldn't it be better to sync our watches and release new versions of
PHP 7.4, 7.3 and possibly 7.2 at the same date, every 4 weeks?
Yes, of course. :)
This can be done by delaying the 7.3 and 7.2 release cycles with one
week. Proposal:
- Tag PHP 7.3.14RC1 on Tuesday Jan 7, Release on Thursday Jan 9
- Tag PHP 7.3.14 on Tuesday Jan 21, Release on Thursday Jan 23
- Tag PHP 7.2.27 (if any) on Jan 21, Release on Jan 23
Small changes would be needed to
https://www.php.net/supported-versions.phpLet us give the 7.3 RMs a New Years Eve
We're planning to shorten the RC phase of 7.4.1 by one week, so that
7.2.26, 7.3.13 and 7.4.1 will be released on December, 19th. If we
would postpone by a week, we'd have to release these on December, 26th,
which doesn't look appealing, neither for RMs nor for users.
Thanks,
Christoph