plan: tern 1.0 (the stable release)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
This issue coordinates the 1.0 release across issues #27–#34. Start by reading those linked issues to understand the release commitments, especially the format migration, recovery and upgrade verification, first run gaps, platform scope, and secret path review. Done means the listed commitments are resolved and the 1.0 compatibility caveat can be retired.
Written by the indexing model from the issue text.
Description
tern 0.1.x already shipped a feature-complete, daily-driver SSH client (that was epic::v1, now done). 1.0 is a different kind of release: it is where the "until 1.0, a minor version may break things" caveat is retired. So 1.0 is not more features — it is the commitments that become permanent the moment a stranger trusts the app with their data.
The commitment that can't be walked back
- #28 — on-disk formats get a version field + migration path
Prove the headline promise
- #29 — recovery path walked end to end on a clean Mac
- #30 — 0.1.x → 1.0 upgrade verified
Close the last first-run gaps
- #31 — waiting-for-input vs connecting state (gaps D2)
- #32 — empty states with a primary action (gaps L10)
- #33 — start-up memory peak explained or accepted (gaps F7)
Decide scope, make trust explicit
- #27 — platform scope: macOS-only 1.0, Windows/Linux stay preview
- #34 — adversarial review of the secret paths
Out of scope for 1.0: mosh / serial / telnet (gaps S11), local shell (gaps T13, dropped).
- Dominant language
- Rust
- Stars
- 2
- Forks
- 2
- Avg merge
- 1h 59m
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from your-moon/tern
-
kind::feature triage::needed
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
vault: the "Save the password … in tern's vault?" offer lands before the shell prompt and mixes with itPossibly taken @itskamol claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
kind::feature triage::needed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
crate: spate-kafka documentation priority: medium
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
balovess/aria2_rust#88 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
agent-self
Difficulty 1/5 Under an hour Newbie friendliness 88/100
yologdev/yoyo-evolve#1154 ·