Propose arbitrary cookbook identiers via new API endpoint
Clarify design constraints for arbitrary ID feature.
Added initial draft of platform support policy
Update ChefDK Mac support
Added missing RHEL row
Give an example of extended cookbook data in "list" API
Add bulk artifact API
Update Gentoo, Arch, OpenSUSE; add clarifications for upstream vendor
lifecycle support terminology per @danielsdeleo
Damn I don't know how to <table>
Accept most modifications from @coderanger
It's ok if Omnitruck goes into Yolo mode, it just can't fail
Forgot Ubuntu under ChefDK. Also, added OmniOS releases
Remove CVT jargon, just mention what we're doing with 'post-build verification'
Fix incorrect Solaris information
Tighten up the language around what we will do for PRs about unsupported OSes.
Spell out 'Oracle' -> 'Oracle Enterprise Linux'
Missing period at end of sentence.

Per our discussion that this RFC is "aspirational", I've added what I think is the desired target list
for Chef-DK platforms. The diff shows exactly the delta between where we are today and where it sounds
like we want to be (modulo my error about RHEL 5.x which isn't supported today).
Again, since this is aspirational: we want to support EL7 as a target platform for server binaries.
First draft of template verification RFC
Fix typos
Allow multiple verify blocks
Verify all file-based resources