kingchenc
d59cd44043
* docs: standardise language naming and add binding security sections Canonical binding list everywhere: Rust, Python, Node.js, WASM, C, C++, C#, Go, Java, R. Use C# (not .NET) as the language label, WASM (not WebAssembly) in prose, and frame the C ABI as a hub rather than a list item. - Bump stale indicator counts (200+ -> 514) and family count (sixteen -> twenty-four) in the Node/Python/WASM and docs READMEs. - Add a short Security section to all eight binding READMEs. - Relabel benchmark rows (C -> C / C++, C# / .NET -> C#). - Fix the 'language stecker' wording in the C#/Go/R API intros. - Documentation only; no code or public API changes. * release.yml: extend install snippets and expose version output Add the missing registry installs to the release body (dotnet, go, Gradle/ Maven Central, r-universe) alongside cargo/pip/npm, and expose a v-stripped 'version' output from the tag step for the Gradle coordinate. Also fix the C-ABI language order in the assets note (C# before Go). * release.yml: correct the release body (10 languages, all registries) Reframe the tagline to '10 languages' (native Rust/Python/Node.js/WASM + a C ABI hub for C, C++, C#, Go, Java, R) instead of '4 language registries', note that C#/Java/Go/R publish to NuGet/Maven/Go/r-universe via their own jobs, and tidy the Node.js label and the C-ABI hub list.
38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# Roadmap
|
|
|
|
This roadmap describes the project's direction at a high level. It is
|
|
intentionally non-binding: priorities shift with feedback and available time,
|
|
and the authoritative, up-to-date view of planned work is the
|
|
[issue tracker](https://github.com/wickra-lib/wickra/issues). Shipped changes
|
|
are recorded in [`CHANGELOG.md`](CHANGELOG.md).
|
|
|
|
## Status
|
|
|
|
Wickra is **pre-1.0**. The public API is largely stable but may still change in
|
|
minor releases; breaking changes are called out in the changelog.
|
|
|
|
## Themes
|
|
|
|
- **Indicator coverage.** Continue broadening the indicator catalogue across
|
|
families (trend, momentum, volatility, volume, statistics, market profile,
|
|
and more), each with the same streaming/batch parity and test guarantees.
|
|
- **API stabilization toward 1.0.** Settle the public `Indicator` and
|
|
`BarBuilder` traits and the binding surfaces, then commit to semantic
|
|
versioning stability for a 1.0 release.
|
|
- **Performance.** Keep per-tick updates O(1) and maintain the benchmark suite;
|
|
investigate further allocation and cache improvements.
|
|
- **Bindings parity.** Keep the Python, Node.js and WASM bindings — plus
|
|
the C ABI and the C#, Go, Java and R bindings generated from it — in lockstep with the
|
|
Rust core, including type stubs and platform coverage.
|
|
- **Documentation.** Maintain a deep-dive page per indicator on
|
|
<https://docs.wickra.org>, plus quickstarts and cookbook material.
|
|
- **Project health.** Maintain test coverage, static and dynamic analysis,
|
|
signed releases, and supply-chain monitoring.
|
|
|
|
## How to influence the roadmap
|
|
|
|
Open or comment on an issue, or start with the
|
|
[feature-request template](.github/ISSUE_TEMPLATE/feature_request.md).
|
|
Well-scoped proposals and pull requests are the most effective way to move an
|
|
item forward.
|