Skip to content

Arctyk ITSM Versioning Guide

This document defines how versions are assigned and advanced across the lifecycle of Arctyk ITSM.

Arctyk ITSM follows Semantic Versioning 2.0.0 with optional pre-release suffixes to communicate stability during development.

Current baseline

v0.4.3

Source of truth: the current version is defined in pyproject.toml and should not be manually edited in multiple places.

Version format

Arctyk versions use:

Meaning

  • MAJOR — Breaking changes, incompatible data model changes, or major architecture shifts
  • MINOR — New features added in a backward-compatible way
  • PATCH — Bug fixes, small improvements, maintenance releases
  • TAG — Optional stability tag: dev, alpha, beta, rc
  • NUMBER — Iteration number for the tag (e.g., -dev.2, -beta.1)

Examples

  • 0.3.1-dev.4
  • 0.4.0-alpha.0
  • 0.5.0-beta.2
  • 0.7.0-rc.1
  • 1.0.0

Stability tags

Tag Meaning Typical usage
-dev In-development, unstable Active daily development
-alpha Experimental snapshot Early preview of a new feature set
-beta Feature complete, needs testing Stabilization and user testing
-rc Release candidate Final QA before a stable release
(none) Stable release Production-ready

What counts as PATCH vs MINOR vs MAJOR

Use this as the default decision rule:

  • PATCH: bug fixes, UI polish, CSS/layout refinements, non-breaking refactors, perf improvements
  • MINOR: new user-facing capability, new workflow step, new module/app, new screens, new exports/imports (backward-compatible)
  • MAJOR: breaking URL/API changes, breaking data migrations, auth/permissions redesign that breaks existing behaviour, major workflow semantics change

Version roadmap

Phase Range Stage Focus
v0.3.x Development Core stabilization Timezone consistency, Celery integration, recurring tickets, inventory/asset management polish
v0.4.x Alpha Feature expansion Modular app design, changelog app, import/export, CI/CD integration
v0.5.x Beta Integration testing Role-based access, unit & integration tests, API documentation
v0.6.x Beta UX/UI refinement UI polish, admin cleanup, user documentation
v0.7.x RC Release candidate Final testing, performance tuning, migration stability
v1.0.0 Stable Production release First production-ready release of Arctyk ITSM
v1.1+ Stable Iteration Analytics, integrations, new modules

Example progression

  • v0.3.0-dev.0 → initial development baseline
  • v0.3.1-dev.1 → bug fixes + small refinements during dev
  • v0.4.0-alpha.0 → begin modularization phase
  • v0.5.0-beta.0 → feature complete, begin stabilization/testing
  • v0.7.0-rc.0 → release candidate for 1.0
  • v1.0.0 → stable production release

Automation

Arctyk uses bumpver to manage versions. The source of truth is stored in pyproject.toml.

Read the Versioning Tools docs: Versioning Tools →