-
-
Notifications
You must be signed in to change notification settings - Fork 805
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
Enhancements for Future Release tracking #397
Comments
I would be happy to finish #384, but I do need some pointers on what still needs to be done. |
@miguelaferreira Awesome! I've been focusing on getting a workable CI going, so I need to finish up a few changes I made yesterday to get a clean run. |
Sure. Please ping me when you're ready and I'll rebase and test. |
Updated to remove Chef 11 from the support list. |
Hey guys, Just a small question: when do you think the 3.0 version of this cookbook will be available? Got a legacy Chef set up that I'm bringing up to date that still uses v 1.8 of this cookbook, but if 3.0 comes out soonish I'd rather wait for it instead of upgrading to 2.7. Thanks! |
@miketheman any chance you can release @tas50 PR #422 so that we have a working 2.X branch that resolves a lot of folks problems? Thanks for taking the time to look at this. |
@miketheman do you want/need help maintaining and administrating this cookbook? This is a hugely important cookbook for a lot of people's environments and it basically hasn't been touched (including merging relatively simple but essential pull requests) since July... |
@eherot I'd gladly accept help on completing the list as mentioned above. |
Closing due to inactivity. If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What is this?
This issue is meant to help track the open issues that should be resolved before cutting the 3.0.0 release.
It is not exhaustive by any means, but attempts to cover the issues.
It will be updated (edited) as needed, so as to reflect the remaining efforts involved. Comments/other issues will be linked as necessary to this main section.
Release-time test matrix:
Must have for release
error_log/access_log
location (Add support for logging to syslog #388)rake notes
to find)Nice to have
nginx_site 'mysite' { action :enable|disable }
to control symlinkswontfix
The text was updated successfully, but these errors were encountered: