Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can you include 1.6 branch as well #3

Closed
yankeeinlondon opened this issue Sep 25, 2014 · 2 comments
Closed

Can you include 1.6 branch as well #3

yankeeinlondon opened this issue Sep 25, 2014 · 2 comments

Comments

@yankeeinlondon
Copy link

I will likely be moving to 1.7.x but for now I'm still entrenched in 1.6 and was hoping you'd support a 1.6 branch.

@tianon
Copy link
Contributor

tianon commented Sep 25, 2014

@thresheek I'm still willing to help set up some scripts like we had on the previous branch to help you manage such a thing if you're interested! 😄

@thresheek
Copy link
Collaborator

The main reason 1.6 (well, stable as we call it) exists is to provide a stable interface for third-party modules - it does not mean 1.7 (current mainline) is unstable - actually it's vice-versa, as only critical bugfixes are merged to stable branch; mainline gets all the fixes.

In general, we recommend deploying mainline branch all the time, see http://nginx.com/blog/nginx-1-6-1-7-released/ for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants