docs: drop completed release-milestone docs; trim roadmap
Remove RELEASE-0.10-PLAN.md and RELEASE-0.10-TASKS.md now that the 0.10.0 milestone work is finished (history preserved in git). Trim ROADMAP.md to open items only; completed work lives in CHANGELOG.md. Version stays 0.10.0 — this release is not yet tagged/shipped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
+4
-25
@@ -1,30 +1,9 @@
|
||||
# Roadmap
|
||||
|
||||
This file tracks planned GoSentry work that is larger than a single bug fix.
|
||||
Completed work is recorded in [CHANGELOG.md](CHANGELOG.md), not here.
|
||||
|
||||
## Completed: Release 0.10.0
|
||||
## Open Items
|
||||
|
||||
**Refactoring Follow-Ups (T6.1)**
|
||||
|
||||
File-size guidelines have been addressed:
|
||||
- `src/ui/jobs_view.go` split into `jobs_view.go` + `jobs_toolbar.go` and
|
||||
`jobs_details.go` to bring it under the ~250 UI file guideline.
|
||||
- `src/app/operations_test.go` remains at 536 lines (soft limit); revisit when
|
||||
next editing if file size becomes a barrier.
|
||||
|
||||
**Post-Field-Test Cleanup (T6.2)**
|
||||
|
||||
Stale diagnostics and obsolete compatibility code removed:
|
||||
- Removed autostart-migration code.
|
||||
- Cleaned `.gitignore` and `.dockerignore` of YAML import rules.
|
||||
- Kept startup-timing History instrumentation for future performance tracking.
|
||||
|
||||
**Delivery And Packaging (T7.1, T7.2)**
|
||||
|
||||
Portable distribution variants complete:
|
||||
- Windows portable `.zip`: `scripts\package-windows.bat` builds and bundles
|
||||
`gosentry.exe`, `README.md`, and `CHANGELOG.md`.
|
||||
- Linux portable `.tar.gz`: `scripts/package-linux.sh` builds `linux-amd64`
|
||||
natively and `linux-arm64` via cross-compilation.
|
||||
|
||||
Both formats bundle files at the archive root for direct extraction and use.
|
||||
_No open roadmap items. Release 0.10.0 closed out the refactoring follow-ups,
|
||||
post-field-test cleanup, and portable packaging work._
|
||||
|
||||
Reference in New Issue
Block a user