From 9b1a6cd79d77ab503888ffbcffa269bbe7c59859 Mon Sep 17 00:00:00 2001
From: "kevin.wilder" <kevin.wilder@darkwolfsolutions.com>
Date: Thu, 5 May 2022 17:12:56 +0000
Subject: [PATCH] Charter: Package upgrade docs

---
 charter/PackageRequirements.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/charter/PackageRequirements.md b/charter/PackageRequirements.md
index 4cb64fca50..eec0e5e0dd 100644
--- a/charter/PackageRequirements.md
+++ b/charter/PackageRequirements.md
@@ -48,6 +48,15 @@ Forked upstream helm charts will be configured with the appropriate BigBang _add
 
 In the case where an accepted upstream helm chart does not exist, BigBang will create and maintain it's own custom helm chart for the package in question.  The helm chart will be in conformance with the [Package Standards](#pr-x.-package-standards).
 
+### Documentation for how to upgrade the Package helm charts
+
+The Package chart should include maintenance documentation that describes
+1. The process for upgrading
+2. How to test the upgrade
+3. Documentation for changes made to the upstream chart.
+
+This documentation will be located in each Package repo and named `/docs/DEVELOPMENT_MAINTENANCE.md`. The document should be linked from the top level `/CONTRIBUTING.md` in the "To contribute a change" section item #2.
+
 ## PR-X. Package Standards
 
 The common components that each package will have are defined in the following folder layout:
-- 
GitLab