From b2cc36b7b0a31820b02d4233642139cc80d4b45e Mon Sep 17 00:00:00 2001 From: "netop://ウィビ" Date: Sat, 11 Apr 2026 15:05:04 -0700 Subject: initial commit --- .gitignore | 3 + README.md | 10 + banner.png | Bin 0 -> 213596 bytes favicon.svg | 3 + index.html | 600 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 616 insertions(+) create mode 100755 .gitignore create mode 100644 README.md create mode 100644 banner.png create mode 100644 favicon.svg create mode 100644 index.html diff --git a/.gitignore b/.gitignore new file mode 100755 index 0000000..712a668 --- /dev/null +++ b/.gitignore @@ -0,0 +1,3 @@ +# OS artefacts +.DS_Store +Thumbs.db diff --git a/README.md b/README.md new file mode 100644 index 0000000..7d2f110 --- /dev/null +++ b/README.md @@ -0,0 +1,10 @@ + +![](banner.png "ChronVer banner") + +**ChronVer (Chronological Versioning) is calendar-based versioning.** In the age of rapid software releases, knowing _when_ something released is more important than arbitrary numbers from an outdated versioning system that most people never adhere to anyway. Finally, versioning for the rest of us. + +--- + +This repo contains the homepage of [https://chronver.org](https://chronver.org). + +Find the module and CLI on [JSR](https://jsr.io/@chronver/chronver) or [Github](https://github.com/ChronVer/chronver). diff --git a/banner.png b/banner.png new file mode 100644 index 0000000..4cc1bf5 Binary files /dev/null and b/banner.png differ diff --git a/favicon.svg b/favicon.svg new file mode 100644 index 0000000..d0e99b6 --- /dev/null +++ b/favicon.svg @@ -0,0 +1,3 @@ + + + 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