<p>This project tries to follow the <ahref="https://semver.org/"target="_blank">semver policy</a> - although not followed 100% in the past.</p>
<p>Usually an entry of <spanclass="badge cstyle warning badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-triangle"></i></span><spanclass="badge-content">Breaking</span></span> on the <ahref="../../basics/migration/">What’s new</a> page causes a new major release number.</p>
<p>All other entries on the <ahref="../../basics/migration/">What’s new</a> page will increase the minor release number.</p>
<p>Releases resulting in a new major or minor number are called main release.</p>
<p>Releases containing bugixes only, are only increasing the patch release number. Those releases don’t result in announcements on the <ahref="../../basics/migration/">What’s new</a> page.</p>
<p>Entries on the <ahref="../../basics/migration/">What’s new</a> page are checked and enforced during the <code>version-release</code> GitHub Action.</p>
<h2id="managing-issues">Managing Issues</h2>
<p>Issues are categorized and managed by assigning <ahref="#labels">labels</a> to it.</p>
<p>Once working on an issue, assign it to a fitting maintainer.</p>
<p>When done, close the ticket. Once an issue is closed, it needs to be assigned to next release milestone.</p>
<p>A once released ticket is not allowed to be reopened and rereleased in a different milestone. This would cause the changelog to be changed even for the milestone the issue was previously released in. Instead write a new ticket.</p>
<p>If the issue would cause a new main release due to <ahref="#semver">semver semantics</a> it needs one of the according labels and the matching badge on the <ahref="../../basics/migration/">What’s new</a> page.</p>
<p>You can assign one further label out of the following list to signal readers that development on an open issue is currently halted for different reasons.</p>
<td>This is a topic related to Mermaid itself but not the theme</td>
</tr>
</tbody>
</table>
<h2id="making-releases">Making Releases</h2>
<p>A release is based on a milestone named like the release itself - just the version number, eg: <code>1.2.3</code>. It’s in the maintainers responsiblity to check <ahref="#semver">semver semantics</a> of the milestone’s name prior to release and change it if necessary.</p>
<p>Making releases is automated by the <code>version-release</code> GitHub Action. It requires the version number of the milestone that should be released. The release will be created from the <code>main</code> branch of the repository.</p>
<p>Treat released milestones as immutable. Don’t rerelease an already released milestone. An already released milestone may already been consumed by your users.</p>
<p>During execution of the action a few things are checked. If a check fails the action fails, resulting in no new release. You can correct the errors afterwards and rerun the action.</p>
<p>The following checks will be enforced</p>
<ul>
<li>the milestone exists</li>
<li>there is at least one closed issue assigned to the milestone</li>
<li>all assigned issues for this milestone are closed</li>
<li>if it’s a main release, there must be a new <code><major>.<minor></code> at the beginning of the <ahref="../../basics/migration/">What’s new</a> page</li>
<li>if it’s a patch release, there must be the <code><major>.<minor></code> from the previous release at the beginning of the <ahref="../../basics/migration/">What’s new</a> page</li>
<li>the <ahref="https://mcshelby.github.io/hugo-theme-relearn/basics/history/index.html"target="_blank">History</a> page is updated, including release version, release date and text</li>
<li>the <ahref="https://mcshelby.github.io/hugo-theme-relearn/basics/migration/index.html"target="_blank">What’s new</a> page is updated, including release version, release date and text</li>
<li>the repository is tagged with the version number (eg. <code>1.2.3</code>), the main version number (eg. <code>1.2.x</code>) and the major version number (eg. <code>1.x</code>)</li>
<li>a new entry in the <ahref="https://github.com/McShelby/hugo-theme-relearn/releases"target="_blank">GitHub release list</a> with the according changelog will be created</li>
<li>the <ahref="https://mcshelby.github.io/hugo-theme-relearn/index.html"target="_blank">official documentation</a> is built and deployed</li>
<li>the version number for the <code><meta generator></code> is updated to a temporary and commited (this helps to determine if users are running directly on the main branch or are using releases)</li>
<li>a new milestone for the next patch release is created (this can later be renamed to a main release if necessary)</li>
