release: v0.1.0 packaging and documentation #95

New issue

Open

opened 2026-03-25 18:37:30 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-03-25 18:37:30 +00:00

Problem

v0.1.0 needs a coherent release surface after the scope reduction.

The release should describe Delta as a single-user self-hosted task/calendar tracker with Google Calendar/Tasks sync, CLI access, iCal interop, and NixOS-first deployment docs.

Solution

Push the v0.1.0 git tag only after the roadmap issue is green.
Publish a Forgejo release with a changelog organized around the reduced scope.
Verify the CLI package release path still works.
Keep the NixOS-first service/deploy documentation as the primary production path.
Keep Docker/Compose out unless it is already trivial and does not delay the NixOS path.
Make the README point to deeper docs instead of carrying operational detail itself.

Acceptance criteria

The release notes do not mention removed scope as upcoming launch work.
The release links the self-hosting docs, README, CLI install path, and known limitations.
just ci and release/version checks pass before tagging.

## Problem v0.1.0 needs a coherent release surface after the scope reduction. The release should describe Delta as a single-user self-hosted task/calendar tracker with Google Calendar/Tasks sync, CLI access, iCal interop, and NixOS-first deployment docs. ## Solution - Push the `v0.1.0` git tag only after the roadmap issue is green. - Publish a Forgejo release with a changelog organized around the reduced scope. - Verify the CLI package release path still works. - Keep the NixOS-first service/deploy documentation as the primary production path. - Keep Docker/Compose out unless it is already trivial and does not delay the NixOS path. - Make the README point to deeper docs instead of carrying operational detail itself. ## Acceptance criteria - The release notes do not mention removed scope as upcoming launch work. - The release links the self-hosting docs, README, CLI install path, and known limitations. - `just ci` and release/version checks pass before tagging.

barrettruth commented

2026-03-25 21:49:51 +00:00

v0.1.0 milestone status update:

Closed (implemented):

#67 — jump list and alternate buffer navigation
#91 — calendar refactor (extracted components, quick-create, military time, auto timezone, category colors)

Open (partially done):

#62 — time grid: core grid built, missing drag-and-drop/resize/working hours shading
#70 — queue view: significantly reworked with line numbers, search, vim nav — may be closeable pending visual review
#92 — / UI: core functionality done, specific font/alignment polish still needed

Open (not started):

#58 — locations and meetings integration (no location field in schema yet)
#95 — this issue (release packaging/docs)

Not in v0.1.0 (unchanged):

#93 — undo system
#61 — blocked task dependencies
#44 — reminders
#36 — mobile strategy

v0.1.0 milestone status update: **Closed (implemented):** - #67 — jump list and alternate buffer navigation - #91 — calendar refactor (extracted components, quick-create, military time, auto timezone, category colors) **Open (partially done):** - #62 — time grid: core grid built, missing drag-and-drop/resize/working hours shading - #70 — queue view: significantly reworked with line numbers, search, vim nav — may be closeable pending visual review - #92 — / UI: core functionality done, specific font/alignment polish still needed **Open (not started):** - #58 — locations and meetings integration (no `location` field in schema yet) - #95 — this issue (release packaging/docs) **Not in v0.1.0 (unchanged):** - #93 — undo system - #61 — blocked task dependencies - #44 — reminders - #36 — mobile strategy