-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
@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! 😄 |
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. |
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.
The text was updated successfully, but these errors were encountered: