Files

Gabriel Radureau db09d0ace1 📝 docs(adr): homogenize all 23 ADR headers to canonical format

Audit 2026-05-02 (Tâche 6 Phase A) had identified 3 inconsistent
formats across the ADR corpus :
- F1 list bullets : `* Status:` / `* Date:` / `* Deciders:` (11 ADRs)
- F2 bold fields : `**Status:**` / `**Date:**` / `**Authors:**` (9 ADRs)
- F3 dedicated section : `## Status\n**Value** ✅` (5 ADRs)

Mixed metadata names (Authors / Deciders / Decision Date / Implementation
Date / Implementation Status / Last Updated) and decorative emojis on
status values made the corpus hard to scan or template against.

Canonical format adopted (see adr/README.md for full template) :
    # NN. Title

    **Status:** <Proposed|Accepted|Implemented|Partially Implemented|
                  Approved|Rejected|Deferred|Deprecated|Superseded by ADR-NNNN>
    **Date:** YYYY-MM-DD
    **Authors:** Name(s)
    [optional **Field:** ... lines]

    ## Context...

Transformations applied (via /tmp/homogenize-adrs.py) :
- F1 list bullets → bold fields
- F2 cleanup : `**Deciders:**` → `**Authors:**`, strip status emojis
- F3 sections : `## Status\n**Value** ✅` → `**Status:** Value`
- Strip decorative emojis from `**Status:**` and `**Implementation Status:**`
- Convert any `* Implementation Status:` / `* Last Updated:` /
  `* Decision Drivers:` / `* Decision Date:` to bold equivalents
- Date typo fix : `2024-04-XX` → `2026-04-XX` for ADRs 0018, 0019
  (already noted in PR #17 but here re-applied since branch starts
  from origin/main pre-PR17)
- Normalize multiple blank lines after header (max 1)

21 / 23 ADRs modified. 0010 and 0012 were already conform.
0011 and 0014 do not exist in the repo (cf. README index update).

Body content of each ADR is preserved unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-03 00:27:42 +02:00

1.5 KiB

Raw Blame History

Use Go 1.26.1 as the standard Go version

Status: Accepted Authors: Gabriel Radureau, AI Agent Date: 2026-04-01

Context and Problem Statement

We needed to choose a Go version for the dance-lessons-coach project that provides:

Stability and long-term support
Access to modern language features
Good ecosystem compatibility
Security updates

Decision Drivers

Project requires modern Go features
Need for good dependency compatibility
Desire for long-term support
Team familiarity with recent Go versions

Considered Options

Go 1.25.x - Latest stable version at project start
Go 1.26.1 - Newer version with additional features
Go 1.24.x - More widely adopted but older

Decision Outcome

Chosen option: "Go 1.26.1" because it provides the best balance of modern features, stability, and ecosystem support.

Pros and Cons of the Options

Go 1.26.1

Good, because provides access to latest language improvements
Good, because includes recent security fixes
Good, because has better performance optimizations
Bad, because slightly less battle-tested than older versions

Go 1.25.x

Good, because widely adopted
Good, because very stable
Bad, because missing some newer features
Bad, because would need upgrade sooner

Go 1.24.x

Good, because extremely stable
Bad, because lacks modern features
Bad, because security updates ending soon

1.5 KiB Raw Blame History