2017-10-19 17:06:24 |
Nish Aravamudan |
bug |
|
|
added bug |
2017-10-19 17:06:30 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Bb-series |
|
2017-10-19 17:06:30 |
Nish Aravamudan |
bug task added |
|
php7.1 (Ubuntu Bb-series) |
|
2017-10-19 17:06:30 |
Nish Aravamudan |
nominated for series |
|
Ubuntu Artful |
|
2017-10-19 17:06:30 |
Nish Aravamudan |
bug task added |
|
php7.1 (Ubuntu Artful) |
|
2017-10-19 17:06:46 |
Nish Aravamudan |
description |
There have been a number of microreleases of PHP 7.1 upstream since the last update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to php7.1. A number of critical security and bug-fixes are present in each 7.1.x. Rather than backporting individual patches, I believe it makes significantly more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.1.x:
- 7.1.10: http://php.net/ChangeLog-7.php
The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly.
Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packaging to run the source tests during the build itself.
I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.2.0 (which will probably be present in BB once released, which is why there is no BB task). |
There have been a number of microreleases of PHP 7.1 upstream since the last update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to php7.1. A number of critical security and bug-fixes are present in each 7.1.x. Rather than backporting individual patches, I believe it makes significantly more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.1.x:
- 7.1.10: http://php.net/ChangeLog-7.php
The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly.
Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packaging to run the source tests during the build itself.
I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.2.0. |
|
2017-10-19 17:13:27 |
Nish Aravamudan |
php7.1 (Ubuntu Artful): assignee |
|
Nish Aravamudan (nacc) |
|
2017-10-19 17:13:28 |
Nish Aravamudan |
php7.1 (Ubuntu Bb-series): assignee |
|
Nish Aravamudan (nacc) |
|
2017-10-19 17:13:31 |
Nish Aravamudan |
php7.1 (Ubuntu Bb-series): status |
New |
In Progress |
|
2017-10-19 17:13:33 |
Nish Aravamudan |
php7.1 (Ubuntu Artful): status |
New |
In Progress |
|
2017-10-19 17:17:32 |
Nish Aravamudan |
php7.1 (Ubuntu Bb-series): status |
In Progress |
Invalid |
|
2017-10-19 17:35:31 |
Nish Aravamudan |
php7.1 (Ubuntu Bb-series): status |
Invalid |
In Progress |
|
2017-10-19 23:31:51 |
Nish Aravamudan |
description |
There have been a number of microreleases of PHP 7.1 upstream since the last update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to php7.1. A number of critical security and bug-fixes are present in each 7.1.x. Rather than backporting individual patches, I believe it makes significantly more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.1.x:
- 7.1.10: http://php.net/ChangeLog-7.php
The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly.
Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packaging to run the source tests during the build itself.
I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.2.0. |
There have been a number of microreleases of PHP 7.1 upstream since the last update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to php7.1. A number of critical security and bug-fixes are present in each 7.1.x. Rather than backporting individual patches, I believe it makes significantly more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.1.x:
- 7.1.10: http://php.net/ChangeLog-7.php
The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly.
Our php7.1 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packaging to run the source tests during the build itself.
I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.2.0.
We already had an MRE for php7.0 in X and Y, and this is the corresponding source package in AA. |
|
2017-10-31 12:14:00 |
Launchpad Janitor |
php7.1 (Ubuntu Bionic): status |
In Progress |
Fix Released |
|
2017-10-31 15:45:17 |
Nish Aravamudan |
cve linked |
|
2016-1283 |
|
2017-10-31 16:15:25 |
Nish Aravamudan |
bug task deleted |
php7.1 (Ubuntu Artful) |
|
|
2017-10-31 16:15:34 |
Nish Aravamudan |
summary |
[MRE] Please update to latest upstream release 7.1.10 |
Please update to latest upstream release 7.1.10 |
|