﻿<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text" xml:lang="en">Leicmin</title>
  <link type="application/atom+xml" href="https://mfgames.com/leicmin/atom.xml" rel="self" />
  <link type="text/html" href="https://mfgames.com/leicmin/" rel="alternate" />
  <updated>2026-04-18T17:43:18Z</updated>
  <id>https://mfgames.com/leicmin/</id>
  <author>
    <name>D. Moonfire</name>
  </author>
  <rights>Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International</rights>
  <entry>
    <title>Semantic Versioning (Leicmin)</title>
    <link rel="alternate" href="https://mfgames.com/blog/2026/04/12/semantic-versioning/" />
    <updated>2026-04-12T05:00:00Z</updated>
    <id>https://mfgames.com/blog/2026/04/12/semantic-versioning/</id>
    <category term="leicmin" scheme="https://mfgames.com/categories/" label="Leicmin" />
    <content type="html">&lt;p&gt;&lt;a href="//d.moonfire.us/blog/2026/04/04/leicmin/"&gt;Six months ago&lt;/a&gt;, we started on a new project called &lt;a href="/leicmin/"&gt;Leicmin&lt;/a&gt; to provide an application for managing members of subscriber groups along with a naieve implementation of age verification checks for those who enjoy the &amp;ldquo;spicer&amp;rdquo; side of creation.&lt;/p&gt;
&lt;p&gt;We were lucky to have an early adopter who helped us iron out some of the more egregarious bugs that were in the application, but there is a still a long way to go. But it is nice to have an instance &amp;ldquo;in the wild&amp;rdquo; as it were.&lt;/p&gt;
&lt;p&gt;This also marks the point where Lecimin is going to have proper semantic versioning, at least for releases. This is important because there was a lot of going back and redoing Postgres migrations which would then require a full install to work.&lt;/p&gt;
&lt;p&gt;Moving forword (e.g., after v0.3.0), the retroactive database changes will only happen between one tag and another. So, if you do use it (and &lt;a href="//d.moonfire.us/contact/"&gt;let us know&lt;/a&gt; if you want to), stick with version tags instead of going directly against &lt;code&gt;main&lt;/code&gt;.&lt;/p&gt;
</content>
  </entry>
</feed>
