# Which version to use in production - 1.2.x or 1.3.x **URL:** \ **Category:** NGINX\ **Created:** [April 21, 2013, 3:32pm UTC](https://www.ruby-forum.com/t/which-version-to-use-in-production-1-2-x-or-1-3-x/228415 "2013-04-21T15:32:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gadh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/e19adc/32.png) [@gadh](https://www.ruby-forum.com/u/gadh)\ **Post date:** [April 21, 2013, 3:32pm UTC](https://www.ruby-forum.com/t/which-version-to-use-in-production-1-2-x-or-1-3-x/228415/1 "2013-04-21T15:32:09Z")
i know that 1.3.x is development version, but is it stable enough to be used in production? as stated here: > **[Re: nginx keep using more and more memory](https://forum.nginx.org/read.php?2,221377,221390#msg-221390)** > > Hi, We are using nginx to proxy to 4 back end servers. And we terminate SSL at nginx. We use nginx in a somewhat special way in that we make 1 HTTP GET and the back-end servers give a very very long (essentially never-ending) response. trouble is... Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then its basic functionality is about 1 year old, and the main changes in it are bug fixes and few features taken from 1.3 after thorough testing ? My main goal of course is to use the latest stable version , and i saw many bug fixes in 1.3 that did not enter the stable 1.2 branch (such as in 1.3.16 - subrequest fixes) Posted at Nginx Forum: > **[which version to use in production - 1.2.x or 1.3.x](https://forum.nginx.org/read.php?2,238512,238512#msg-238512)** > > i know that 1.3.x is development version, but is it stable enough to be used in production? as stated here: http://forum.nginx.org/read.php?2,221377,221390#msg-221390 Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then its basic... ---
**Author:** ![gadh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/e19adc/32.png) [@gadh](https://www.ruby-forum.com/u/gadh)\ **Post date:** [April 22, 2013, 6:23pm UTC](https://www.ruby-forum.com/t/which-version-to-use-in-production-1-2-x-or-1-3-x/228415/2 "2013-04-22T18:23:18Z")
Hello! On Sun, Apr 21, 2013 at 09:31:52AM -0400, gadh wrote: > - subrequest fixes) > Generally both development aka mainline and stable versions are ok > for production. Development might need a bit more attention on > upgrades though, especially if you use 3rd party modules - as it > occasionally introduces various changes (including API ones). – Maxim D. > **[nginx: donation](http://nginx.org/en/donation.html)** ---
**Author:** ![gadh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/e19adc/32.png) [@gadh](https://www.ruby-forum.com/u/gadh)\ **Post date:** [April 23, 2013, 10:12am UTC](https://www.ruby-forum.com/t/which-version-to-use-in-production-1-2-x-or-1-3-x/228415/3 "2013-04-23T10:12:41Z")
thanks, where can i see the API changes between 1.2.x and 1.3.x ? i currently use subrequest in 1.2.8 and in 1.3.16 the filter module is not called and the browser waits forever (so it does not go to backend also) Posted at Nginx Forum: > **[Re: which version to use in production - 1.2.x or 1.3.x](https://forum.nginx.org/read.php?2,238512,238573#msg-238573)** > > i know that 1.3.x is development version, but is it stable enough to be used in production? as stated here: http://forum.nginx.org/read.php?2,221377,221390#msg-221390 Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then its basic... ---
**Author:** ![gadh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/e19adc/32.png) [@gadh](https://www.ruby-forum.com/u/gadh)\ **Post date:** [April 23, 2013, 4:15pm UTC](https://www.ruby-forum.com/t/which-version-to-use-in-production-1-2-x-or-1-3-x/228415/4 "2013-04-23T16:15:32Z")
Hello! On Tue, Apr 23, 2013 at 04:12:14AM -0400, gadh wrote: > thanks, where can i see the API changes between 1.2.x and 1.3.x ? i > currently use subrequest in 1.2.8 and in 1.3.16 the filter module is not > called and the browser waits forever (so it does not go to backend also) All commits can be seen in nginx source code repository. Commit logs usually indicate API changes done, either explicitly or implicitly. Note though that not everything you can do with nginx internal structures is a part of the API. And in many cases “it now waits forever” problems are results of code worked in previous versions by chance or due to some implementation details which were changed in new versions. – Maxim D. > **[nginx: donation](http://nginx.org/en/donation.html)**