# 3.3.0-beta4, version numbering, bug fixes

**URL:** https://forum.vassalengine.org/t/3-3-0-beta4-version-numbering-bug-fixes/10696
**Category:** Development
**Created:** [June 6, 2020, 2:23pm UTC](https://forum.vassalengine.org/t/3-3-0-beta4-version-numbering-bug-fixes/10696 "2020-06-06T14:23:51Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [June 6, 2020, 2:23pm UTC](https://forum.vassalengine.org/t/3-3-0-beta4-version-numbering-bug-fixes/10696/1 "2020-06-06T14:23:51Z")

</div>

The changes in master over 3.3.0-beta3 right now are few and limited in scope. I’m reasonably confident that we won’t get bug reports because of them, and that we won’t get many additional bug reports from anything else new which has already appeared in a beta.

I think it’s quite possible that we would get a lot of bug reports due to the changes which have open PRs right now—not because I think they’re incorrect, but because they’re the sorts of changes which affect modules, saves, and logs, which makes it more likely that there are effects we haven’t anticipated.

So:

- I would like to release beta4 roughly as master is now.
- I would like to release 3.3.0 from that if there aren’t any new issues introduced in beta4.

That will get all of the fixes which are already done and have had some user testing out to users. No one will be worse off for not having the bug fixes which are in PR now, as they deal with preexisting bugs. Then we can put these new fixes into 3.3.1.

Related thing:

We’ve put the Subversion version number into builds the entire time we’ve been using Subversion. On switching to Git, we no longer have an increasing version number we can use for that, because Git commits are SHA1 hashes and are effectively random. However, “git describe --tags” can produce a version string which consists of the most recent tag reachable on a branch, the number of commits beyond that tag, and the commit hash. E.g., when I run that on master right now I get “3.3.0-beta3-80-gf8ef2523”. The “80” means that we’re 80 commits ahead of 3.3.0-beta3. That’s basically a build number, and we could use it that way for naming builds.

If that sounds reasonable to everyone, I’ll update the version string parser to handle these.

Thoughts?

---

_[View the full topic](https://forum.vassalengine.org/t/3-3-0-beta4-version-numbering-bug-fixes/10696)._