来自 Ubuntu 14.04 的 NGINX 1.4.7 与最新版本 NGINX 1.8.0
NGINX 1.4.7 from Ubuntu 14.04 vs latest version NGINX 1.8.0
我注意到 ubuntu 14.04 中的 NGINX 标准版本与 NGINX website 上的（!stable）版本相比确实很旧，后者目前是 1.8.0。
为什么会有这么大的差异？是否建议在生产 Web 服务器上手动更新到最新稳定版本的 nginx？
我希望获得 SPDY 3.1 以改进加载时间。值得付出努力吗？
Nginx 不断更新，新版本包含 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 使用 'unstable' 分支，我完全同意他们：
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.
我不知道有人在使用比他们提供的发行版更新的 nginx 版本时遇到问题 — 考虑到配置问题和安全问题，所以我认为这样做是完全安全的。
我注意到 ubuntu 14.04 中的 NGINX 标准版本与 NGINX website 上的（!stable）版本相比确实很旧，后者目前是 1.8.0。
为什么会有这么大的差异？是否建议在生产 Web 服务器上手动更新到最新稳定版本的 nginx？
我希望获得 SPDY 3.1 以改进加载时间。值得付出努力吗？
Nginx 不断更新，新版本包含 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 使用 'unstable' 分支，我完全同意他们：
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.
我不知道有人在使用比他们提供的发行版更新的 nginx 版本时遇到问题 — 考虑到配置问题和安全问题，所以我认为这样做是完全安全的。