Added remaining content

Signed-off-by: Lisa Barry <[email protected]>

components/docs-chef-io/content/habitat/package_naming_conventions.md

@@ -27,7 +27,16 @@ When more than one major version of the package will be supported, the project u
   - The value of **name** should match the name of the project it represents, plus the major and minor version of the package being supported (as a suffix).
   - The plan file should be located within a directory of the same name (including the suffix) in this repository.
 
+  {{< note >}}
+  Romantic versions appear like a SemVer in format but may/can/will introduce breaking changes as part of a “minor” update. This results in Version X.Y having a breaking change versus X.Z.
+  {{< /note >}}
+
+  For example, core/foo3_0, core/ foo3_1, core/ foo3_2, and/or core/foo3_3.
+
+- If the project does not use SemVer:
+  For example, builder-api, perl.
+  The packages will be reviewed package to package and refresh to refresh.
+
 {{< note >}}
-Romantic versions appear like a SemVer in format but may/can/will introduce breaking changes as part of a “minor” update. Resulting in Version X.Y having a breaking change versus X.Z
-Example: core/foo3_0, core/ foo3_1, core/ foo3_2, and/or core/foo3_3
-{{< /note >}} 
+Even though a package name may be altered to include a major (and minor) version suffix, package versions are never altered from their project's source. For example, if the package uses a DateVer schema where it is YYYYMMDD, this will not be reformatted to YYYY.MM.DD. This is to ensure the CVE detection process and automated build and detection systems can refer to the exact publishers' versions.
+{{< /note >}}

components/docs-chef-io/content/habitat/support_and_usage_thresholds.md

@@ -0,0 +1,29 @@
++++
+title = "Support and usage thresholds"
+description = ""
+gh_repo = "habitat"
+
+[menu]
+  [menu.habitat]
+    title = "Support and usage thresholds"
+    identifier = "habitat/packages/support/package_support/support_and_usage_thresholds"
+    parent = "habitat/packages/package_support"
+    weight = 15
++++
+
+Refer to the following sections for details about the support and usage thresholds.
+
+## Support threshold
+
+For packages that are not dependencies for Progress Chef Tools:
+
+- There should be no published End of Life (EOL) date within the first two years of the LTS-YYYY support duration at the time of consideration. If the OEM drops support or does not provide a fix to known vulnerabilities during the LTS timeframe, no updates will be made available.
+- There should be no open High or Critical CVEs for that package at the time of consideration. If any released package has a Critical/High CVE post-release, it will be fixed as part of the next minor/directed refresh.
+- It should have a valid licensing model that allows Progress Chef to distribute it as a Habitat Package.
+
+## Usage threshold
+
+A requested package will be added for backlog prioritization if it belongs to one of the following categories:
+
+- Commonly-used development tools/programming languages
+- High demand COTS