mix/gosentry
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
7dafa82b2108ea481b2ae2b462ea840bb49b071b
gosentry/docs/ROADMAP.md
T
mixeme 20390fe476 Add 0.10.0 milestone plan; trim ROADMAP to portable packaging 
Add docs/RELEASE-0.10-PLAN.md covering the open roadmap follow-ups plus
per-job overlap policy, run-time statistics, one-line activity entries,
log-name fix, and 720p window sizing. Drop the non-portable delivery
formats (.deb, installer, AppImage, Flatpak, winget) from ROADMAP.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-24 00:46:23 +03:00

2.1 KiB
Raw Blame History

Roadmap

This file tracks planned GoSentry work that is larger than a single bug fix.

Refactoring Follow-Ups

Loose ends found while verifying the refactoring against its Definition of done. The architecture target is reached and verified on Windows and Linux.

  • File-size guidelines exceeded (soft limits). The DoD suggests no src/ui file over ~250 lines and no single file over ~400:

    • src/ui/jobs_view.go — 415 lines (over both the ~250 UI target and the ~400 cap).
    • src/app/operations_test.go (536) also exceeds 400.

    These are soft ("~") limits; revisit when next touching those files rather than splitting purely for line count.

Post-Field-Test Cleanup

After real-world use confirms the main workflows, clean up temporary stabilization code and development scaffolding.

Cleanup checklist:

  • Review and remove debug-oriented diagnostics that are no longer useful.
  • Remove excessive defensive checks once behavior is proven and covered by the right tests.
  • Remove obsolete compatibility cleanup, such as old autostart migration code, after the transition window is over.
  • Delete stale generated files and old build artifacts from local/release flows.
  • Revisit tests and remove ones that only lock in temporary implementation details instead of real user-facing behavior.
  • Simplify README notes that were useful during early setup but are too noisy for normal users.
  • Recheck .gitignore, Docker scripts, and packaging scripts for rules or branches that only supported early experiments.

Delivery And Packaging

Keep a single portable binary as the baseline delivery format. It is simple to test, easy to copy between machines, and matches the current storage model where runtime YAML files live next to the executable by default.

Planned delivery variants:

  • Windows portable .zip with gosentry.exe, README.md, and CHANGELOG.md.
  • Linux portable .tar.gz archives for linux-amd64 and linux-arm64.

Portable builds keep settings and jobs next to the executable.

Initial priority:

  1. Windows portable .zip.
  2. Linux portable .tar.gz for amd64 and arm64.
Reference in New Issue View Git Blame Copy Permalink