Roadmap and releases
Releases are driven by milestones, not dates. Each version is a usable stopping point, and the order puts safe upgrades first and sensitive features before anything is shared publicly.
- The full relationship model, with step, half and in-law relatives worked out for you
- Built-in encrypted backup, with an automatic safety copy before database changes
- Update notices and a "What's new" popup for admins
- Link an existing account to a person
- Your data is protected across upgrades from this release on
The road to 1.0
0.1 · It runs
DoneThe delivery chain: a public repository, published images, one compose file and a single tree view. Alpha, and data could be wiped.
0.2 · A tree you can trust
PublishedRelationships, add-relative, backup and restore, update notices, four color schemes. The data promise starts here.
0.3 · See the family
In progressAll four chart views, relationship finder, search, timeline and map, photos with encrypted upload, the in-app Restore button, and account management.
0.4 · Email, sign-in and notifications
PlannedInvites and resets by email, OpenID Connect single sign-on with roles set by group, authenticator-app sign-in for SuperAdmins, birthday and remembrance reminders.
0.5 · Research records
PlannedSources, citations, places, stories, duplicate merge with 30-day undo, a change history, and optional automatic transcription of handwritten scans.
0.6 · Health, and privacy done right
PlannedConditions and surgeries, private by default, with a dedicated security review and a permanent role-by-role test suite.
0.7 · Reports, import and export
PlannedCore reports as print, PDF and text, plus GEDCOM 5.5.1 import and export.
1.0 · Stable
PlannedRelease candidates for a security review, accessibility and mobile passes, a large-tree load test, complete docs, and a live read-only demo of the Darwin–Wedgwood family.
After 1.0
Ideas, in order1.1 storage and polish (S3, Word output, family book) · 1.2 and 1.3 DNA · 1.4 approvals and two-factor sign-in for every role · 1.5 research tools. A 2.0 only if the data model must change.
How releases work
Versioning
Semantic versions. Before 1.0 each minor release is a milestone and patches are bug fixes only. The version number is not a measure of size, so new features after 1.0 do not need a 2.0.
Your data
Migrations only move forward and keep your data. Every upgrade path is tested, and the app asks you to back up first when a release changes the database.
Support
Only the newest release is supported, with fixes shipped as a new patch. That keeps one maintainer's work honest, so upgrading is made as safe and easy as possible.
Something missing?
Bugs and work left out of a release are tracked as issues on GitHub. Questions and ideas are welcome there too.