Override the chef version for release.
pulling untagged 11-stable for testing
bump to 11-stable
pin chef version to 11.14.0
bumping to 11.14.2

11.14.0 will not be released due to regressions
pin Angrychef version for 11.14.2 release
Merge pull request #210 from opscode/schisamo/angrychef-11.14.2

pin Angrychef version for 11.14.2 release
remove ffi-yajl software dep

we're just going to pull from the chef.gemspec now
Bump `angrychef` build iteration to prepare for another release
Merge pull request #211 from opscode/schisamo/remove-ffi-yajl

Remove ffi-yajl dep from Chef software def
Pin versions for release 11.14.6.
Temporary pin of chef version to 11.16.0.rc.0
Build from the 11-dsc branch
Add required deps for publishing to Artifactory
Optionally publish to Artifactory using the Omnibus publisher

If the release script is called with the `—-publish-to-artifactory`
option each artifact will be published to Artifactory in addition to the
normal Omnitruck publishing tasks.
Vendor openssl/openssl-windows from omnibus-software

From omnibus-software#40f75279c5198d5be6a11642dd6bb1e534bfbba5
Update to openssl 1.0.1i

Pull from a1ec576c
Update openssl-windows to 1.0.0n for security fixes

https://www.openssl.org/news/secadv_20140806.txt
11.16.0.rc.0
Output a SemVer compliant build version string

We currently use the `:git_describe` version for all chef-client
projects. This build version format does not respect
`Omnibus::Config.append_timestamp` which in turn causes two different
builds to produce packages named identically. This can wreck havoc on
when packages are published to backends like Omnitruck and Artifactory.