makiolaj/calendula
1
0
Fork 0
Code Issues 1 Pull Requests 6 Actions Releases 7 Activity

release: cut v1.0.0 — first public release
Some checks failed
CI / ci (push) Successful in 13m23s
Details
CI / ci (pull_request) Has been cancelled
Details
Build and Release to F-Droid / ci (push) Has been cancelled
Details
Build and Release to F-Droid / build-and-deploy (push) Has been cancelled
Details

Browse Source 
Version bumped to 1.0.0 / 7. No code changes beyond the version — 1.0.0 is the
accumulated v0.1 → v0.6 work (all V1 screens, full event read, filter, settings,
onboarding polish) declared release-ready. CHANGELOG [1.0.0] summarises the
shipped feature set; ROADMAP/STATE mark V1 complete.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Luc Makiola
2026-06-11 09:24:47 +02:00
parent e290c92d78
commit 3697a58e5b
4 changed files with 35 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.planning/ROADMAP.md
View File

@@ -10,7 +10,7 @@
| v0.4 | Event Detail (S4) + humanized recurrence | complete |
| v0.5 | Calendar filter (M3) + Settings (M4) | complete |
| v0.6 | Full event read — surface every readable field | complete |
| v1.0 | Polish pass, F-Droid release | pending |
| v1.0 | First public release — polish pass, F-Droid | complete |
Delivery ran ahead of the original table: Day view (S3) shipped in v0.3 and
Event Detail (S4) in v0.4, so the Filter/Settings milestone became v0.5.
@@ -44,14 +44,14 @@ Deliberately out of v0.6:
- `CATEGORIES`, `ATTACH` — not reliably exposed by `CalendarContract`
(provider limitation, not our choice)
## v1.0 — First Public Release
## v1.0 — First Public Release — shipped 2026-06-11
All V1 features shipped, polished, on F-Droid. Read-only calendar.
Remaining before v1.0: a UI polish/QA pass.
All V1 features shipped, polished, on F-Droid. Read-only calendar. Cut directly
after v0.6 (full event read) plus the onboarding-screen polish pass.
### Polish backlog (pre-1.0)
- ~~Redesign the initial grant-access (permission) screen~~ — **done**
(Material 3 Expressive onboarding, shipped on the v0.6.0 branch)
(Material 3 Expressive onboarding, shipped in v0.6.0 / v1.0.0)
## v2.0 — Write Support

12
.planning/STATE.md
View File

@@ -4,10 +4,10 @@
## Status
**Milestone:** v0.6 — Full event read (complete)
**Phase:** All V1 screens done and the read model is now complete — the detail
view surfaces every readable `CalendarContract` field. Next up is a UI
polish/QA pass before v1.0
**Milestone:** v1.0.0 — First public release (shipped 2026-06-11)
**Phase:** V1 is complete and released. All screens done, the read model
surfaces every readable `CalendarContract` field, and the onboarding screen
got its Material 3 Expressive polish pass. Next horizon is v2.0 (write support)
## Progress
@@ -30,5 +30,5 @@ polish/QA pass before v1.0
## Next
1. UI polish / QA pass across all views before v1.0
2. F-Droid release of v1.0
1. v1.0.0 released — monitor the F-Droid build/publish
2. Plan v2.0 (write support: create / edit / delete, quick-add, conflict UX)