Separate names with a comma.
Discussion in 'Nginx and PHP-FPM news & discussions' started by eva2000, Apr 13, 2017.
yup way Nginx versioning works is
nginx 1.10 stable jumps to nginx 1.12 stable (1.12.0)
nginx 1.11 mainline jumps to nginx 1.13 mainline
so basically 1.11 mainline code goes to 1.10 stable now
So Centmin Mod will be going from nginx 1.11 to 1.13 mainline when available as essentially nginx 1.11 and 1.12 stable are the same. Though 1.12.0 is looking good on Centmin Mod 123.09beta01
So, upgrade now to 1.12.0 or stay on 1.11.13?
both essentially the same so 1.11.13 is fine. I suspect 1.13.0 when it's out will be close to same as 1.11.13 too at first.
1.12.0 I guess?
I am confused with this unlogic version numbers.
1.11.13 is better than 1.12.0
1.11.13 is most likely the same as 1.12.0
And after a some time there will be 1.11.14 and 1.12.1
What will be newest, better, stable.
it is so unlogic.
1.12.1 = upcoming stable branch
1.13.0 = upcoming mainline version
Just like how Ubuntu versioning works.
see explanation of odd main numbers 1.11 = mainline and even main numbers 1.12 = stable Introducing NGINX 1.10 and 1.11 - NGINX
So 1.13.x will be mainline - and still not exist
1.12.x is new one but not better than existed 1.11.x
So I will have to wait for 1.13.0 to upgrade from 1.11.13, and avoid 1.12.x
So big complication, confuzing...
Just follow what Centmin Mod users = old branch 1.11, 1.13, 1.15 for mainline branches. So 1.11.13 > 1.13.0 > 1.13.1 > 1.13.2 etc etc
OK, waiting for 1.13.0
Great to see another really exciting stable release of Nginx.
On to HTTP/2 serverpush and TLS 1.3 support now!
I've actually had a dream about those announcements
Forget server push, is not going to happen in the near feature
I hope so but thats another story.