<liitemscopeitemtype="https://schema.org/ListItem"itemprop="itemListElement"><aitemprop="item"href="../../../pir/index.html"><spanitemprop="name">Cap'n Hugo Relearrrn Theme</span></a><metaitemprop="position"content="1">></li>
<p>This project tries t' follow th' <ahref="https://semver.org/"target="_blank">semver policy</a> - although not followed 100% 'n th' past.</p>
<p>Usually an entry o' <spanclass="badge cstyle warning badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-triangle"></i></span><spanclass="badge-content">Break'n</span></span> on th' <ahref="../../../basics/migration/">What’s new</a> plank causes a new major release number.</p>
<p>All other entries on th' <ahref="../../../basics/migration/">What’s new</a> plank will increase th' minor release number.</p>
<p>Releases result'n 'n a new major or minor number be called main release.</p>
<p>Releases contain'n bugixes only, be only increas'n th' patch release number. Those releases don’t result 'n announcements on th' <ahref="../../../basics/migration/">What’s new</a> plank.</p>
<p>Entries on th' <ahref="../../../basics/migration/">What’s new</a> plank be checked an' enforced dur'n th' <code>version-release</code> GitHub Act'n.</p>
<h2id="managing-issues">Manag'n Issues</h2>
<p>Issues be categorized an' managed by assign'n <ahref="#labels">labels</a> t' it.</p>
<p>Once work'n on an issue, assign it t' a fitt'n maintainer.</p>
<p>When done, close th' ticket. Once an issue be closed, it needs t' be assigned t' next release milestone.</p>
<p>A once released ticket be not allowed t' be reopened an' rereleased 'n a different milestone. This would cause th' changelog t' be changed even fer th' milestone th' issue was previously released 'n. Instead write a new ticket.</p>
<p>If th' issue would cause a new main release due t' <ahref="#semver">semver semantics</a> it needs one o' th' accord'n labels an' th' match'n badge on th' <ahref="../../../basics/migration/">What’s new</a> plank.</p>
<p>Ye can assign one further label out o' th' follow'n list t' signal readers that development on an open issue be currently halted fer different reasons.</p>
<td>This be a topic related t' Merrrmaid itself but not th' theme</td>
</tr>
</tbody>
</table>
<h2id="making-releases">Mak'n Releases</h2>
<p>A release be based on a milestone named like th' release itself - just th' version number, eg: <code>1.2.3</code>. It’s 'n th' maintainers responsiblity t' check <ahref="#semver">semver semantics</a> o' th' milestone’s name prior t' release an' change it if necessary.</p>
<p>Mak'n releases be automated by th' <code>version-release</code> GitHub Act'n. It requires th' version number o' th' milestone that should be released. Th' release will be created from th' <code>main</code> branch o' th' repository.</p>
<p>Treat released milestones as immut'ble. Don’t rerelease an already released milestone. An already released milestone may already been consumed by yer users.</p>
<p>Dur'n execut'n o' th' act'n a few th'ns be checked. If a check fails th' act'n fails, result'n 'n no new release. Ye can correct th' errors afterwards an' rerun th' act'n.</p>
<p>Th' follow'n checks will be enforced</p>
<ul>
<li>th' milestone exists</li>
<li>there be at least one closed issue assigned t' th' milestone</li>
<li>all assigned issues fer this milestone be closed</li>
<li>if it’s a main release, there must be a new <code><major>.<minor></code> at th' beginn'n o' th' <ahref="../../../basics/migration/">What’s new</a> plank</li>
<li>if it’s a patch release, there must be th' <code><major>.<minor></code> from th' previous release at th' beginn'n o' th' <ahref="../../../basics/migration/">What’s new</a> plank</li>
<li>th' repository be tagged wit' th' version number (eg. <code>1.2.3</code>), th' main version number (eg. <code>1.2.x</code>) an' th' major version number (eg. <code>1.x</code>)</li>
<li>a new entry 'n th' <ahref="https://github.com/McShelby/hugo-theme-relearn/releases"target="_blank">GitHub release list</a> wit' th' accord'n changelog will be created</li>
<li>th' <ahref="https://mcshelby.github.io/hugo-theme-relearn/index.html"target="_blank">official documentat'n</a> be built an' deployed</li>
<li>th' version number fer th' <code><meta generator></code> be updated t' a temporary an' commited (this helps t' determine if users be runn'n directly on th' main branch or be us'n releases)</li>
<li>a new milestone fer th' next patch release be created (this can later be renamed t' a main release if necessary)</li>
