From b2cc36b7b0a31820b02d4233642139cc80d4b45e Mon Sep 17 00:00:00 2001 From: "netop://ウィビ" Date: Sat, 11 Apr 2026 15:05:04 -0700 Subject: initial commit --- index.html | 600 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 600 insertions(+) create mode 100644 index.html (limited to 'index.html') diff --git a/index.html b/index.html new file mode 100644 index 0000000..66b4ba9 --- /dev/null +++ b/index.html @@ -0,0 +1,600 @@ + + + + + + + + + + + + + + + + + + + + ChronVer • Versioning for the rest of us + + + + + + + + + + + + + +
+

ChronVer

+

Versioning for the rest of us

+
+ + + +
+ +
+ +
+

Format

+ + 

+YYYY.MM.DD[.CHANGESET][-FEATURE|-break]
+
+
+ +
+

Examples

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
VersionDescription
2025.07.21Released July 21st, 2025
2025.07.21.1First hotfix today
2025.07.21.3Third change today
2025.07.21-featureFeature branch made today
2025.07.21.1-featureFeature branch with changeset
2025.07.21.1-breakBreaking change
+
+ +
+

FAQ

+ +
+ Why not just use dates? +

ChronVer is dates, but with a structured format that supports multiple releases per day, feature branches, and breaking change indicators.

+
+ +
+ What about semantic compatibility? +

ChronVer can indicate breaking changes with the -break suffix. For situations where semantic versioning is crucial, stick with SemVer.

+
+ +
+ How do I migrate from SemVer? +
    +
  1. Choose your first ChronVer date (usually next release)
    2. +
  2. Update your build tools to use chronver increment
    3. +
  3. Update documentation to explain the new format
    4. +
  4. Consider keeping a mapping in your CHANGELOG
    5. +
+
+ +
+ Can I use both ChronVer and SemVer? +

Absolutely! Here's how your project could use ChronVer for releases and SemVer for API versions:

+ 

+{
+  "apiVersion": "v2.1.0",
+  "version": "2024.07.19.1"
+}
+
+

Easy-peasy.

+
+
+ +
+

Comparison with SemVer

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AspectChronVerSemVer
ClarityImmediately shows when releasedRequires lookup
PlanningAligns with calendar schedulesFeature-driven
Communication"The April release""Version 3.2.1"
SortingChronological by defaultArbitrary without context
CompatibilityTime-based breaking changesAPI contract based
Best forTime-sensitive releasesLibrary compatibility
+
+ + + + + + -- cgit v1.2.3