Note: this document is meant for developers. If you have no interest in pyfa development, then this doesn't offer you much
In early 2018, as part of a large effort to update pyfa's codebase to Python 3, pyfa also updated it's versioning standard to use PEP-440. As such, version strings in pyfa must be strictly compatible with with PEP-440, and must not raise an exception with packaging.version.Version.
In early 2019, pyfa moved to a process of automated versions. Before these changes, for every release, developers had to manually update the version information in config.py to match the intended release version, and then tag that commit properly. Since 2019, pyfa versioning has been automated by the use of git describe --tags. As such, pyfa versions are wholly determined by tags in git - literal tagged commits are considered releases, and other builds that
When AppVeyorr or Travis-CI (coming soon) picks up a build job, one of the