找到你要的答案

Q:NGINX 1.4.7 from Ubuntu 14.04 vs latest version NGINX 1.8.0

Q:Nginx 1.4.7从Ubuntu 14.04和最新版本的nginx 1.8.0

I noticed that the standard version of NGINX in ubuntu 14.04 is really old compared to the (!stable) version on the NGINX website, which is currently 1.8.0.
Why is there such a big difference? Is it recommend to manually update to the latest stable version of nginx on a production web server? I was hoping to get SPDY 3.1 to get improved load-time. Is it worth the effort?

I noticed that the standard version of NGINX in ubuntu 14.04 is really old compared to the (!stable) version on the NGINX website, which is currently 1.8.0.
Why is there such a big difference? Is it recommend to manually update to the latest stable version of nginx on a production web server? I was hoping to get SPDY 3.1 to get improved load-time. Is it worth the effort?

answer1: 回答1:

Nginx is constantly being updated and new versions contains many new features which you might want to use and it's highly recommended to use latest available stable or unstable version. Nginx Inc. recommends to use 'unstable' branch, and I totally agree with them:

How Branch Renumbering Works

The branch renumbering is part of our annual checkpoint process where we fork off a “stable” (no new features) branch from the “mainline” (feature development) branch. NGINX 1.8 was forked as the new stable branch from the 1.7 mainline branch, and the 1.7 branch is renumbered to 1.9. We are no longer supporting 1.6 (the former stable branch) or doing development in 1.7.

In NGINX nomenclature, stable (now version 1.8) means that the feature set is fixed; only critical bug fixes are committed to that branch. Stable does not necessarily mean more reliable or more bug-free. In fact, the mainline branch (now 1.9) is generally regarded as more reliable because we commit a wider range of bug fixes to it, not just the critical fixes merged into the stable branch. On the other hand, any changes to the stable branch are very unlikely to affect the operation of third-party modules, whereas in the mainline branch the addition of new features might do so. To get a full view of how we do our branch renumbering (complete with pictures), check out last year’s post.

I am unaware of anyone encountered problems when using newer nginx version than their distributive provided — considering both configuration issues and security ones, so in my opinion it's completely safe to do so.

Nginx的不断更新和新版本包含了很多新特性,你可能想要使用它的强烈推荐使用最新的可用的稳定或不稳定的版本。Nginx公司推荐使用“不稳定”的分支,我完全同意他们的观点:

Branch Renumbering的作品

部门编号是我们的年度检查过程中,我们复制一个“稳定”(没有新功能)分公司从“主线”(功能开发)分支。nginx的1.8叉从1.7条主线分支的新的稳定的分,和1.7分改为1.9。我们不再支持1.6(前稳定的分支)或在1.7做发展。

In NGINX nomenclature, stable (now version 1.8) means that the feature set is fixed; only critical bug fixes are committed to that branch. Stable does not necessarily mean more reliable or more bug-free. In fact, the mainline branch (now 1.9) is generally regarded as more reliable because we commit a wider range of bug fixes to it, not just the critical fixes merged into the stable branch. On the other hand, any changes to the stable branch are very unlikely to affect the operation of third-party modules, whereas in the mainline branch the addition of new features might do so. To get a full view of how we do our branch renumbering (complete with pictures), check out last year’s post.

我不知道任何人在遇到问题的时候,使用新的nginx的版本比他们分配提供配置和安全问题的考虑,所以我认为它是完全安全的这样做。

ubuntu  nginx  webserver  spdy