Skip to content

Introduce semantic versioning #116

@simonmicro

Description

@simonmicro

Currently, we have...

  • an old Changelog, which is not really being maintained anymore (also in the wiki)
  • a master / next branch (the first should be renamed to main)
  • no tags / GH-releases to track changes

So, I propose:

  • Add tags using semantic versions (not year.month(.day) pattern like used in the Changelog before) → see notes of Semantic version #140
  • Add Github releases for new tags → see notes of Semantic version #140
  • Start fresh on version 1.0.0 (I do not want to go back in time and re-version / reevaluate for breaking changes everything)
  • Update actions to build tagged versions
  • Add contributing-guide to the wiki, specifying to work against the next-branch
  • Drop the changelog, as it is replaced with tags & releases
  • The current docker-tags are just historic reasons at this point (we have no python2 anymore anyways)
    • add -minimal, -full suffix to main, next, [version-tag] images
    • keep the classic tags as non-documented backward compatibility

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions