|
|
@@ -1380,6 +1380,20 @@
|
|
|
Proposal Process
|
|
|
</a>
|
|
|
|
|
|
+</li>
|
|
|
+
|
|
|
+ <li class="md-nav__item">
|
|
|
+ <a href="#release-planning" class="md-nav__link">
|
|
|
+ Release Planning
|
|
|
+ </a>
|
|
|
+
|
|
|
+</li>
|
|
|
+
|
|
|
+ <li class="md-nav__item">
|
|
|
+ <a href="#support-questions" class="md-nav__link">
|
|
|
+ Support & Questions
|
|
|
+ </a>
|
|
|
+
|
|
|
</li>
|
|
|
|
|
|
<li class="md-nav__item">
|
|
|
@@ -1537,6 +1551,20 @@
|
|
|
Proposal Process
|
|
|
</a>
|
|
|
|
|
|
+</li>
|
|
|
+
|
|
|
+ <li class="md-nav__item">
|
|
|
+ <a href="#release-planning" class="md-nav__link">
|
|
|
+ Release Planning
|
|
|
+ </a>
|
|
|
+
|
|
|
+</li>
|
|
|
+
|
|
|
+ <li class="md-nav__item">
|
|
|
+ <a href="#support-questions" class="md-nav__link">
|
|
|
+ Support & Questions
|
|
|
+ </a>
|
|
|
+
|
|
|
</li>
|
|
|
|
|
|
<li class="md-nav__item">
|
|
|
@@ -1650,8 +1678,24 @@ develop and release big changes. Significant changes include for example:
|
|
|
* changing the behavior of the controller significantly</p>
|
|
|
<p>Please create a document in the <code>design/</code> directory based on the template <code>000-template.md</code>
|
|
|
and fill in your proposal. Open a pull request in draft mode and request feedback. Once the proposal is accepted and the pull request is merged we can create work packages and proceed with the implementation.</p>
|
|
|
+<h2 id="release-planning">Release Planning</h2>
|
|
|
+<p>We have a <a href="https://github.com/orgs/external-secrets/projects/2/views/1">GitHub Project Board</a> where we organize issues on a high level. We group issues by milestone. Once all issues of a given milestone are closed we should prepare a new feature release. Issues of the next milestone have priority over other issues - but that does not mean that no one is allowed to start working on them.</p>
|
|
|
+<p>Issues must be <em>manually</em> added to that board (at least for now, see <a href="https://github.com/github/roadmap/issues/286">GH Roadmap</a>). Milestones must be assigned manually as well. If no milestone is assigned it is basically a backlog item. It is the responsibility of the maintainers to (1) assign new issues to the GH Project, (2) add a milestone if needed and (3) add appropriate labels.</p>
|
|
|
+<p>If you would like to raise the priority of an issue for whatever reason feel free to comment on the issue or ping a maintainer.</p>
|
|
|
+<h2 id="support-questions">Support & Questions</h2>
|
|
|
+<p>Providing support to end users is an important and difficult task.
|
|
|
+We have three different channels through which support questions arise:</p>
|
|
|
+<ol>
|
|
|
+<li>Kubernetes Slack <a href="https://kubernetes.slack.com/archives/C017BF84G2Y">#external-secrets</a></li>
|
|
|
+<li><a href="https://github.com/external-secrets/external-secrets/discussions">GitHub Discussions</a></li>
|
|
|
+<li>GitHub Issues</li>
|
|
|
+</ol>
|
|
|
+<p>We use labels to identify GitHub Issues. Specifically for managing support cases we use the following labels to identify the state a support case is in:
|
|
|
+* <code>triage/needs-information</code>: Indicates an issue needs more information in order to work on it.
|
|
|
+* <code>triage/not-reproducible</code>: Indicates an issue can not be reproduced as described.
|
|
|
+* <code>triage/support</code>: Indicates an issue that is a support question.</p>
|
|
|
<h2 id="cutting-releases">Cutting Releases</h2>
|
|
|
-<p>The external-secrets project is released on a as-needed basis. Feel free to open a issue to request a release. Details on how to cut a release can be found in the <code>RELEASE.md</code> file in the repo.</p>
|
|
|
+<p>The external-secrets project is released on a as-needed basis. Feel free to open a issue to request a release. Details on how to cut a release can be found in the <a href="../contributing-release/">release</a> page.</p>
|
|
|
|
|
|
|
|
|
</article>
|
Docs