<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SIG Release on Kubernetes Contributors</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/release/</link><description>Recent content in SIG Release on Kubernetes Contributors</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/release/index.xml" rel="self" type="application/rss+xml"/><item><title>SIG Release Charter</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/release/charter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/release/charter/</guid><description>&lt;h2 id="scope">Scope&lt;/h2>
&lt;ul>
&lt;li>Production of Kubernetes releases on a reliable schedule&lt;/li>
&lt;li>Ensure there is a consistent group of community members in place to support the release process across time&lt;/li>
&lt;li>Provide guidance and tooling to facilitate the production of automated releases&lt;/li>
&lt;li>Serve as a tightly integrated partner with other SIGs to empower SIGs to integrate their repositories into the release process&lt;/li>
&lt;/ul>
&lt;h3 id="in-scope">In scope&lt;/h3>
&lt;ul>
&lt;li>Ensuring quality Kubernetes releases
&lt;ul>
&lt;li>Defining and staffing release roles to manage the resolution of release blocking criteria&lt;/li>
&lt;li>Defining and driving development processes (e.g. merge queues, cherrypicks) and release processes
(e.g. burndown meetings, cutting pre-releases) with the intent of meeting the release schedule&lt;/li>
&lt;li>Managing the creation of release specific artifacts, including:
&lt;ul>
&lt;li>Code branches&lt;/li>
&lt;li>Binary artifacts&lt;/li>
&lt;li>Container Images&lt;/li>
&lt;li>Release notes&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Continually improving release and development processes
&lt;ul>
&lt;li>Working closely with SIG Contributor Experience to define and build tools to facilitate release process (e.g. dashboards)&lt;/li>
&lt;li>Working closely with SIG Testing to determine and implement tests, automation, and labeling required for stable releases&lt;/li>
&lt;li>Working with downstream communities responsible for packaging Kubernetes releases&lt;/li>
&lt;li>Working with other SIGs to agree upon the responsibilities of their SIG with respect to the release&lt;/li>
&lt;li>Defining and collecting metrics related to the release in order to measure progress over each release&lt;/li>
&lt;li>Facilitating release retrospectives&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Collaborating with downstream communities which build artifacts from Kubernetes releases&lt;/li>
&lt;/ul>
&lt;h3 id="out-of-scope">Out of scope&lt;/h3>
&lt;h4 id="support">Support&lt;/h4>
&lt;p>SIG Release itself is not responsible for end user support or creation of patches for support streams. There are support forums for end users to ask questions and report bugs, subject matter experts in other SIGs triage and address issues and when necessary mark bug fixes for inclusion in a patch release.&lt;/p></description></item></channel></rss>