If you install NGINX from a third‑party repository, you might not have control over which version is deployed, and the repository might not keep pace with the mainline and stable branches. If you have pinned your installation to the official NGINX repository, the next time you update you will get the latest 1.6 or 1.7 build as appropriate. The main reason to use the stable branch is that you are concerned about possible impacts of new features, such as incompatibility with third‑party modules or the inadvertent introduction of bugs in new features. We recommend that in general you deploy the NGINX mainline branch at all times. We don’t make the same commitment concerning the mainline, where new features can affect the operation of third‑party modules. On the other hand, changes in the stable branch are very unlikely to affect third‑party modules. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as for the stable branch. Note that stable does not mean more reliable or more bug‑free. We’ve extended error logging, added cache revalidation directives, added SMTP pipelining, added buffering options for FastCGI, improved support for MP4 streaming, and extended handling of byte‑range requests for streaming and caching. We integrated community contributions for SSL support for uwsgi.
Over the last year, the mainline has seen the introduction of SPDY 3.1 support, authentication via subrequests, SSL session ticket support, IPv6 support for DNS, and PROXY protocol support. We operate a time‑based release process, so you can expect to see new mainline releases approximately once per month, with exceptional releases when necessary. We develop new features and all bug fixes in the mainline branch. Only major bug fixes are committed to that version. In NGINX nomenclature, “stable” means that no new features are added (the feature set is stable). Version 1.6 is forked from version 1.5 as the new “stable” branch, and 1.5 is renumbered to 1.7 as the “mainline” branch We continue active development on the renumbered mainline branch. This is an annual checkpoint where we take the current mainline (feature) branch and fork it to a stable (no new features) branch. NGINX 1.6 was forked from the current mainline branch (1.5), which was then renumbered to 1.7. This article explains how we schedule product releases at NGINX, Inc., and explains the significance of this version number change. Today we’re announcing the release of NGINX 1.6 and 1.7.
0 kommentar(er)
