Deployed c7dfa3c
with MkDocs version: 1.5.3
This commit is contained in:
parent
1b73c2701b
commit
dea4249a9c
@ -920,7 +920,7 @@
|
||||
<h1 id="release-engineering-sigcore-wiki">Release Engineering (SIG/Core) Wiki<a class="headerlink" href="#release-engineering-sigcore-wiki" title="Permanent link">¶</a></h1>
|
||||
<h2 id="about">About<a class="headerlink" href="#about" title="Permanent link">¶</a></h2>
|
||||
<p>The Rocky Linux Release Engineering Team (who also refers to themselves as SIG/Core) dedicates themselves to the development, building, management, production, and release of Rocky Linux. This group combines development and infrastructure in a single cohesive unit of individuals that ultimately make the distribution happen.</p>
|
||||
<p>While not a strict Special Interest Group (as defined by <a href="https://wiki.rockylinux.org/special_interest_groups/">the Rocky Linux wiki</a>), the primary, overarching goal (or "interest") is to ensure Rocky Linux is built and released in a complete and functional manner.</p>
|
||||
<p>While not a strict Special Interest Group (as defined by <a href="https://wiki.rockylinux.org/special_interest_groups/">the Rocky Linux wiki</a>), the primary overarching goal (or "interest") is to ensure Rocky Linux is built and released in a complete and functional manner.</p>
|
||||
<h2 id="mission">Mission<a class="headerlink" href="#mission" title="Permanent link">¶</a></h2>
|
||||
<p>Release Engineering strives to ensure a stable distribution is developed, built, tested, and provided to the community from the RESF as a compatible derivative of Red Hat Enterprise Linux. To achieve this goal, some of the things we do are:</p>
|
||||
<ul>
|
||||
|
File diff suppressed because one or more lines are too long
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binary file not shown.
@ -844,12 +844,15 @@
|
||||
<ul>
|
||||
<li>Continuous preparation for upcoming changes from upstream (Fedora and CentOS Stream)</li>
|
||||
<li>Distribution release and maintenance</li>
|
||||
<li>Design and collaboration for the Peridot build system</li>
|
||||
<li>Design and development work to integrate all components together</li>
|
||||
<li>Maintenance of the infrastructure used to build and maintain Rocky Linux (such as ansible roles and playbooks)</li>
|
||||
<li>Working with the testing team with images and a platform to test</li>
|
||||
<li>Providing resources for Special Interest Groups</li>
|
||||
<li>Providing assistance and resources for users within the community</li>
|
||||
</ul>
|
||||
<p>"Why the name SIG/Core?"</p>
|
||||
<p>While not an actual <a href="https://wiki.rockylinux.org/special_interest_groups/">Special Interest Group</a>, the reality is that Release Engineering is ultimately the "core" of Rocky Linux's production. The idea of "SIG/Core" stemmed from the thought that without this group, Rocky Linux would not exist as it is now, so we are "core" to its existence. The other idea was that SIG/Core would eventually branch out to elsewhere. Where this would go, it is uncertain.</p>
|
||||
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user