Mainline is where new features arrive. Think of it kind of like what used to be Firefox Aurora. Stable is snapshots of mainline taken less frequently that are considered suitable for long term use.
Mainline has newer features, but isn't quite a nightly build. Stable has fewer features but is more stable. I use mainline for my needs, including in production.
The really interesting point is that nginx considers mainline to be more reliable than stable because stable does not receive all bug fixes, only the critical ones.
[1] explains which version should you use. (I probably go with mainline).
All the newest features are added to mainline releases. By the time most of the bugs are fixed, their version is renumbered and branch is forked to make a stable release.
[2] is where you see the information about upcoming nginx releases.
Pretty sure it's verifying SSL certificates of the proxied (backend) servers in a reverse proxy configuration-- so that you know you're talking to the backend server that you think you're talking to (in case your internal network gets MITM'd, I guess, or if you're talking to backend servers across a public network).
At least, that's what I gather from the new config options they linked to (the relevant options are the proxy_ssl_* directives).
24 comments
[ 3.0 ms ] story [ 62.7 ms ] threadHere's the diff between 1.8.0 and 1.7.12
http://trac.nginx.org/nginx/changeset/01d52c2b460da263fd1557...
[1] http://nginx.org/en/CHANGES-1.8
Tired of being a beta tester.
But nice feature list.
If it were versioned 1.8.1 it'd be a mainline release which is more experimental.
Mainline has newer features, but isn't quite a nightly build. Stable has fewer features but is more stable. I use mainline for my needs, including in production.
[1] explains which version should you use. (I probably go with mainline).
All the newest features are added to mainline releases. By the time most of the bugs are fixed, their version is renumbered and branch is forked to make a stable release.
[2] is where you see the information about upcoming nginx releases.
[1] http://nginx.com/blog/nginx-1-6-1-7-released/ [2] http://trac.nginx.org/nginx/roadmap
At least, that's what I gather from the new config options they linked to (the relevant options are the proxy_ssl_* directives).