Platform support policy proposal

There is a fair amount of confusion about the specific operating system platforms, platform versions, etc. that Chef Software, Inc. supports for its products. This RFC will clarify this by calling out the individual operating systems and their releases as explicitly supported or not.
You probably need to distinguish between CVT tests and omnibus build pipeline tests.

Having CVT tests for OEL, RHEL and CentOS is pretty useless.  I don't expect to see any differences between them at the level of the chef rspec tests.  Actual packaging of an omnibus chef client would be better.  Still I'd argue that most of the time spent maintaining all these different flavors of substantially identical distros would be better spent expanding the matrix to other systems (for chef-client).

We should also distinguish between support levels and infrastructure.  There's this assumption that to be tier 1 we need builders and testers, and I don't understand why we can't break this assumption.  The tier 1 classification should be towards support.  And we certainly have tier 1 support for OEL, RHEL and Amazon today, even though we don't have builders.  In recent history the only bug I can think of was around this line in the postrm of the RPM we ship, which we promptly fixed:

https://github.com/opscode/omnibus-chef/blob/master/package-scripts/chef/postrm#L29

So very :-1: on CVT testers for RHEL variants.  And even :-1: on omnibus testers for chef-client for RHEL variants, but :+1: on Tier 1 support for them (and Amazon as well -- which is a pure-cloud distro so jenkins testers gets complicated there unless we patch in test-kitchen).