Point release with recent merges
A few small fixes merged recently makes this good to cut a release I think.
@tas50 any objections? Would you prefer to standardize any of the cookbook release process stuff like stove gem or related prior to that?
It would be nice to get a release out. At Chef we use stove to do the push to Supermarket since it strips away everything but the bare minimum files. That might be a nice tool to adopt here, but it's not absolutely necessary.
It would be great to get a release out with 34b7b84c9007b285e3488c1d01dc2d3377e56a41 in it. =)
I need to carve out some time to get RHEL working correctly and then I can release what I have. I'm tempted to cut a Debian/Ubuntu release right now though since every platform is broken on Supermarket and pushing master would at least get something working.
We're waiting on #275 to get merged in first, as this cookbook wont converge without it. Once we've got a clean converging cookbook we'll release.
Thanks!
Waiting on some upstream fixes to come through: https://github.com/computology/packagecloud-cookbook/pull/53
How is release looking for 1.0.5?
@NoMotion we're still waiting for the package cloud repo to merge Tims latest changes/fixes. I've pinged them again to see if they can ship
Can we expect a release any time soon? Looks like this attribute can't be used with the current version: https://github.com/sous-chefs/graphite/blob/master/attributes/uwsgi.rb#L27
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.