v2: kick off v2-dev — version constant + roadmap
Freeze the classic line on main (tagged v1.0-classic) and open the v2 development branch. Add a firmware version constant (2.0.0-dev) reported in the boot banner so the daemon can tell classic from v2, and document the phased v2 plan in docs/v2-roadmap.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,10 @@
|
||||
#pragma once
|
||||
|
||||
// Clawdmeter firmware version.
|
||||
//
|
||||
// The "classic" line — the stable Waveshare AMOLED-2.06 port plus the working
|
||||
// Windows BLE daemon — is frozen on the `main` branch and tagged v1.0-classic.
|
||||
// Active development (multi-app launcher, on-screen soundpad, Now Playing,
|
||||
// Home Assistant control, richer desktop companion) lives on `v2-dev`.
|
||||
// See docs/v2-roadmap.md.
|
||||
#define CLAWDMETER_VERSION "2.0.0-dev"
|
||||
Reference in New Issue
Block a user