v0.3.2 is tagged and packaged, but the documentation and release notes still describe the 0.2 line. Milestone 8 is closed in the tracker and shipped in the tag, yet ROADMAP.md still lists it as future work.
Current behaviour
README.md version badge still says v0.2.1.
README feature list omits instrument detect, multi-pass averaging, presets, 3D convex hull, touch, and the Ubuntu 22.04 glibc fix.
ROADMAP.md section 3 still lists Milestone 8 as future with empty checkboxes.
Gitea release v0.3.2 has an empty body.
src/js/delaunator.min.js is unused after #89 (dead 8 KB). index.html does not reference it.
Merged feature branches are still on the remote: fix/103-stage1-file-browse, feat/89-3d-convex-hull-touch, feat/88-profiling-presets.
ROADMAP: move M8 items to Completed (checkboxes [x]). Keep M9 / M10 as future. Add a Hotfix v0.3.1 / v0.3.2 subsection (#103 browse, #108 glibc).
Write a proper v0.3.2 release body (glibc 22.04 .deb, asset names). Editing a published Gitea release is a maintainer action; include the markdown in the PR description so it can be pasted.
Delete src/js/delaunator.min.js. Grep must find no Delaunator usage except comments.
Delete merged branches listed above.
Suggested v0.3.2 release body:
## ICCery v0.3.2
glibc compatibility hotfix for Debian/Ubuntu 22.04 `.deb` packages.
### Fixes
- **#108**: Linux CI runner moved to Ubuntu 22.04 so the `.deb` no longer requires `GLIBC_2.39`.
### Also in the 0.3 line
- **#103 / v0.3.1**: Stage 1 file browse via backend `select_target_file`.
- **v0.3.0 / Milestone 8**: instrument detect, multi-pass averaging UI, presets, 3D convex hull, touch controls, Windows `.exe` resolution.
Files
README.md
ROADMAP.md
src/js/delaunator.min.js (delete)
Acceptance criteria
README version badge matches package.json / Cargo.toml / tauri.conf.json (0.3.2).
ROADMAP Completed includes M8; Future starts at M9.
No remaining references to M8 as unstarted.
delaunator.min.js gone; grep finds no Delaunator usage except comments.
| Field | Value |
|---|---|
| Labels | `Kind/Documentation`, `Priority/Medium` |
| Priority | Medium |
| Milestone | v0.3.3 hotfix |
| Related | #65, #80, v0.3.0, v0.3.1, v0.3.2 |
| Branch | `docs/v0.3.2-hygiene` (from `development`) |
| Pair with | — |
## Description
v0.3.2 is tagged and packaged, but the documentation and release notes still describe the 0.2 line. Milestone 8 is closed in the tracker and shipped in the tag, yet `ROADMAP.md` still lists it as future work.
## Current behaviour
- `README.md` version badge still says `v0.2.1`.
- README feature list omits instrument detect, multi-pass averaging, presets, 3D convex hull, touch, and the Ubuntu 22.04 glibc fix.
- `ROADMAP.md` section 3 still lists Milestone 8 as future with empty checkboxes.
- Gitea release `v0.3.2` has an empty body.
- `src/js/delaunator.min.js` is unused after #89 (dead 8 KB). `index.html` does not reference it.
- Merged feature branches are still on the remote: `fix/103-stage1-file-browse`, `feat/89-3d-convex-hull-touch`, `feat/88-profiling-presets`.
## Proposed solution
- README badge → `v0.3.2`.
- README Key Features: add instrument detect, multi-pass average, presets, 3D convex hull, touch, glibc 22.04 note.
- ROADMAP: move M8 items to Completed (checkboxes `[x]`). Keep M9 / M10 as future. Add a **Hotfix v0.3.1 / v0.3.2** subsection (#103 browse, #108 glibc).
- Write a proper v0.3.2 release body (glibc 22.04 `.deb`, asset names). Editing a published Gitea release is a maintainer action; include the markdown in the PR description so it can be pasted.
- Delete `src/js/delaunator.min.js`. Grep must find no `Delaunator` usage except comments.
- Delete merged branches listed above.
Suggested v0.3.2 release body:
```markdown
## ICCery v0.3.2
glibc compatibility hotfix for Debian/Ubuntu 22.04 `.deb` packages.
### Fixes
- **#108**: Linux CI runner moved to Ubuntu 22.04 so the `.deb` no longer requires `GLIBC_2.39`.
### Also in the 0.3 line
- **#103 / v0.3.1**: Stage 1 file browse via backend `select_target_file`.
- **v0.3.0 / Milestone 8**: instrument detect, multi-pass averaging UI, presets, 3D convex hull, touch controls, Windows `.exe` resolution.
```
## Files
- `README.md`
- `ROADMAP.md`
- `src/js/delaunator.min.js` (delete)
## Acceptance criteria
- [ ] README version badge matches `package.json` / `Cargo.toml` / `tauri.conf.json` (`0.3.2`).
- [ ] ROADMAP Completed includes M8; Future starts at M9.
- [ ] No remaining references to M8 as unstarted.
- [ ] `delaunator.min.js` gone; grep finds no `Delaunator` usage except comments.
- [ ] PR description contains paste-ready v0.3.2 release notes.
- [ ] Stale feature branches deleted after merge.
## Dependencies
None. Docs-only PR. Do not mix with code fixes.
gronod
added this to the v0.3.3 Hot fixes milestone 2026-08-26 15:12:53 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Kind/Documentation,Priority/Mediumdocs/v0.3.2-hygiene(fromdevelopment)Description
v0.3.2 is tagged and packaged, but the documentation and release notes still describe the 0.2 line. Milestone 8 is closed in the tracker and shipped in the tag, yet
ROADMAP.mdstill lists it as future work.Current behaviour
README.mdversion badge still saysv0.2.1.ROADMAP.mdsection 3 still lists Milestone 8 as future with empty checkboxes.v0.3.2has an empty body.src/js/delaunator.min.jsis unused after #89 (dead 8 KB).index.htmldoes not reference it.fix/103-stage1-file-browse,feat/89-3d-convex-hull-touch,feat/88-profiling-presets.Proposed solution
v0.3.2.[x]). Keep M9 / M10 as future. Add a Hotfix v0.3.1 / v0.3.2 subsection (#103 browse, #108 glibc)..deb, asset names). Editing a published Gitea release is a maintainer action; include the markdown in the PR description so it can be pasted.src/js/delaunator.min.js. Grep must find noDelaunatorusage except comments.Suggested v0.3.2 release body:
Files
README.mdROADMAP.mdsrc/js/delaunator.min.js(delete)Acceptance criteria
package.json/Cargo.toml/tauri.conf.json(0.3.2).delaunator.min.jsgone; grep finds noDelaunatorusage except comments.Dependencies
None. Docs-only PR. Do not mix with code fixes.
# docs: README/ROADMAP still describe v0.2.1; v0.3.2 release notes emptyto docs: README/ROADMAP still describe v0.2.1; v0.3.2 release notes emptyResolved via PR #124. Updated
README.mdandROADMAP.mdto reflectv0.3.2, cleaned up legacydelaunator.min.js.