Activity log for bug #1503051

Date Who What changed Old value New value Message
2015-10-05 21:45:13 Thomas Ward bug added bug
2015-10-05 21:45:43 Thomas Ward description This will apply to X-series only. The latest NGINX Mainline release is 1.9.5, which introduces 'breaking' changes to the nginx system. These breaking changes include the removal of the SPDY module, and the replacement of it with the HTTP/2 module. This will pose several upgrade considerations and headaches. The removal of the SPDY module means that all SPDY configuration options will trigger "Unknown directive" errors which will cause nginx to fail to start, and in turn throw dpkg/apt errors about "Failed to Upgrade Package". The introduction of HTTP/2 means, also, that all HTTP/2 configuration options must be added to configurations. In-place configurations which utilize SPDY will fail to operate after an upgrade from Trusty, Vivid, or Wily to X-series. This is a known issue that will happen. I am currently working with NGINX upstream to come up with a 'non-fatal failure' solution for the upgrade, however a release notes entry for the removal of SPDY and the availability of HTTP/2 may be prudent (suggested by Robie Basak via IRC to me). Such entry can be written by me come the time to write X-series release notes. This will apply to X-series only. The latest NGINX Mainline release is 1.9.5, which introduces 'breaking' changes to the nginx system. These breaking changes include the removal of the SPDY module, and the replacement of it with the HTTP/2 module. This will pose several upgrade considerations and headaches. The removal of the SPDY module means that all SPDY configuration options will trigger "Unknown directive" errors which will cause nginx to fail to start, and in turn throw dpkg/apt errors about "Failed to Upgrade Package". The introduction of HTTP/2 means, also, that all HTTP/2 configuration options must be added to configurations. In-place configurations which utilize SPDY will fail to operate after an upgrade from Trusty, Vivid, or Wily to X-series. This is a known issue that will happen. I am currently working with NGINX upstream to come up with a 'non-fatal failure' solution for the upgrade, however a release notes entry for the removal of SPDY and the availability of HTTP/2 may be prudent (suggested by Robie Basak via IRC to me). Such entry can be written by me come the time to write X-series release notes. (A corresponding NGINX bug will be opened after Wily is released, ahead of the 1.9.5 packages being available in Debian)
2015-10-22 10:46:38 Jean-Baptiste Lallement summary X-Series - 'nginx' release notes entry for SPDY/HTTP2 major changes Xenial - 'nginx' release notes entry for SPDY/HTTP2 major changes
2015-10-22 10:47:02 Jean-Baptiste Lallement description This will apply to X-series only. The latest NGINX Mainline release is 1.9.5, which introduces 'breaking' changes to the nginx system. These breaking changes include the removal of the SPDY module, and the replacement of it with the HTTP/2 module. This will pose several upgrade considerations and headaches. The removal of the SPDY module means that all SPDY configuration options will trigger "Unknown directive" errors which will cause nginx to fail to start, and in turn throw dpkg/apt errors about "Failed to Upgrade Package". The introduction of HTTP/2 means, also, that all HTTP/2 configuration options must be added to configurations. In-place configurations which utilize SPDY will fail to operate after an upgrade from Trusty, Vivid, or Wily to X-series. This is a known issue that will happen. I am currently working with NGINX upstream to come up with a 'non-fatal failure' solution for the upgrade, however a release notes entry for the removal of SPDY and the availability of HTTP/2 may be prudent (suggested by Robie Basak via IRC to me). Such entry can be written by me come the time to write X-series release notes. (A corresponding NGINX bug will be opened after Wily is released, ahead of the 1.9.5 packages being available in Debian) This will apply to Xenial only. The latest NGINX Mainline release is 1.9.5, which introduces 'breaking' changes to the nginx system. These breaking changes include the removal of the SPDY module, and the replacement of it with the HTTP/2 module. This will pose several upgrade considerations and headaches. The removal of the SPDY module means that all SPDY configuration options will trigger "Unknown directive" errors which will cause nginx to fail to start, and in turn throw dpkg/apt errors about "Failed to Upgrade Package". The introduction of HTTP/2 means, also, that all HTTP/2 configuration options must be added to configurations. In-place configurations which utilize SPDY will fail to operate after an upgrade from Trusty, Vivid, or Wily to Xenial. This is a known issue that will happen. I am currently working with NGINX upstream to come up with a 'non-fatal failure' solution for the upgrade, however a release notes entry for the removal of SPDY and the availability of HTTP/2 may be prudent (suggested by Robie Basak via IRC to me). Such entry can be written by me come the time to write Xenial release notes. (A corresponding NGINX bug will be opened after Wily is released, ahead of the 1.9.5 packages being available in Debian)
2015-12-15 01:17:35 Thomas Ward description This will apply to Xenial only. The latest NGINX Mainline release is 1.9.5, which introduces 'breaking' changes to the nginx system. These breaking changes include the removal of the SPDY module, and the replacement of it with the HTTP/2 module. This will pose several upgrade considerations and headaches. The removal of the SPDY module means that all SPDY configuration options will trigger "Unknown directive" errors which will cause nginx to fail to start, and in turn throw dpkg/apt errors about "Failed to Upgrade Package". The introduction of HTTP/2 means, also, that all HTTP/2 configuration options must be added to configurations. In-place configurations which utilize SPDY will fail to operate after an upgrade from Trusty, Vivid, or Wily to Xenial. This is a known issue that will happen. I am currently working with NGINX upstream to come up with a 'non-fatal failure' solution for the upgrade, however a release notes entry for the removal of SPDY and the availability of HTTP/2 may be prudent (suggested by Robie Basak via IRC to me). Such entry can be written by me come the time to write Xenial release notes. (A corresponding NGINX bug will be opened after Wily is released, ahead of the 1.9.5 packages being available in Debian) This will apply to Xenial only. ------ NGINX 1.9.6 is pending a merge currently. As a result of this, additional mandates have been given, and additional information made available to me at this time. Firstly, SPDY/HTTP2 support: * SPDY is dead in the nginx packages with this merge/update and future versions - it was replaced with the HTTP/2 modules. * HTTP/2 is disabled in the packages as a result of a Security Team mandate. Those who are hoping to see HTTP/2 support in the Xenial packages of nginx will not see that support as long as that mandate is in place. Secondly, Lua: * Depending on whether Lua 5.1 is kept in or demoted out of Main in Xenial, the nginx-extras package may or may not have Lua module support. This will be determined closer to 16.04 Xenial release, and if necessary a section in the nginx release notes will be written accordingly. Release notes will reflect this closer to release time, when a Release Notes section is written. This bug's description may update again closer to release date.
2015-12-15 14:32:51 Thomas Ward summary Xenial - 'nginx' release notes entry for SPDY/HTTP2 major changes Xenial - 'nginx' release notes entry for upcoming changes
2016-03-03 23:34:15 Thomas Ward description This will apply to Xenial only. ------ NGINX 1.9.6 is pending a merge currently. As a result of this, additional mandates have been given, and additional information made available to me at this time. Firstly, SPDY/HTTP2 support: * SPDY is dead in the nginx packages with this merge/update and future versions - it was replaced with the HTTP/2 modules. * HTTP/2 is disabled in the packages as a result of a Security Team mandate. Those who are hoping to see HTTP/2 support in the Xenial packages of nginx will not see that support as long as that mandate is in place. Secondly, Lua: * Depending on whether Lua 5.1 is kept in or demoted out of Main in Xenial, the nginx-extras package may or may not have Lua module support. This will be determined closer to 16.04 Xenial release, and if necessary a section in the nginx release notes will be written accordingly. Release notes will reflect this closer to release time, when a Release Notes section is written. This bug's description may update again closer to release date. This will apply to Xenial only. ------ NGINX 1.9.6 has been in Xenial for some time. During the NGINX 1.9.6 merge, additional mandates have been given, and additional information made available to me. SPDY/HTTP2 support: * SPDY is dead in the nginx packages with this merge/update and future versions - it was replaced with the HTTP/2 modules. * HTTP/2 is disabled in the packages as a result of a Security Team mandate. Those who are hoping to see HTTP/2 support in the Xenial packages of nginx will not see that support as long as that mandate is in place. Release notes will reflect this closer to release time, when a Release Notes section is written. This bug's description may update again closer to release date.
2016-04-07 15:18:14 Thomas Ward ubuntu-release-notes: status New Invalid