OiO.lk Community platform!

Oio.lk is an excellent forum for developers, providing a wide range of resources, discussions, and support for those in the developer community. Join oio.lk today to connect with like-minded professionals, share insights, and stay updated on the latest trends and technologies in the development field.
  You need to log in or register to access the solved answers to this problem.
  • You have reached the maximum number of guest views allowed
  • Please register below to remove this limitation

How should I set the version number between releases? [closed]

  • Thread starter Thread starter kdavies4
  • Start date Start date
K

kdavies4

Guest
I have a Python project on GitHub (ModelicaRes). I'm trying to follow Semantic Versioning. I post releases the main project site and upload them to PyPI. For the releases, I write the version number in the main __init__.py file (__version__=...). Between releases, I push updates to GitHub (usually on the main branch---nothing fancy).

How should I set the version number for these inter-release updates? The commits are usually working copies. They aren't fully tested, but others may download and use these copies (via GitHub). Usually, I'm not ready to determine the new version number. Lately I've been setting the version number to None and putting an auto-generated "UNRELEASED COPY" file in the base folder with the commit date and other info. However, I'm not convinced this is the best approach.

This may apply to other languages, but right now I'm just interested in Python.

I guess I could try to use an "alpha", "beta", or "rc" suffix on the next version number, but again I don't always know the next version number (could be major or minor or bugfixes only). I also want to keep this simple---not a lot of branching, etc.

Thanks!
<p>I have a Python project on GitHub (<a href="https://github.com/kdavies4/ModelicaRes" rel="noreferrer">ModelicaRes</a>). I'm trying to follow <a href="http://semver.org/" rel="noreferrer">Semantic Versioning</a>. I post releases the main project site and upload them to PyPI. For the releases, I write the version number in the main __init__.py file (<code>__version__=...</code>). Between releases, I push updates to GitHub (usually on the main branch---nothing fancy).</p>

<p>How should I set the version number for these inter-release updates? The commits are usually working copies. They aren't fully tested, but others may download and use these copies (via GitHub). Usually, I'm not ready to determine the new version number. Lately I've been setting the version number to <em>None</em> and putting an auto-generated <a href="https://github.com/kdavies4/ModelicaRes/blob/master/UNRELEASED COPY.md" rel="noreferrer">"UNRELEASED COPY" file</a> in the base folder with the commit date and other info. However, I'm not convinced this is the best approach.</p>

<p>This may apply to other languages, but right now I'm just interested in Python.</p>

<p>I guess I could try to use an "alpha", "beta", or "rc" suffix on the next version number, but again I don't always know the next version number (could be major or minor or bugfixes only). I also want to keep this simple---not a lot of branching, etc.</p>

<p>Thanks!</p>
 

Latest posts

Top