mirror of
https://github.com/alibaba/higress.git
synced 2026-07-28 23:30:29 +08:00
31 lines
1.6 KiB
Markdown
31 lines
1.6 KiB
Markdown
# Higress Roadmap
|
|
|
|
The maintained public Higress roadmap is published on the
|
|
[Higress website](https://higress.ai/en/docs/latest/overview/roadmap/). Its
|
|
source is version controlled in the
|
|
[`higress-group/higress-group.github.io`](https://github.com/higress-group/higress-group.github.io/blob/main/src/content/docs/latest/en/overview/roadmap.md)
|
|
repository.
|
|
|
|
Roadmap entries describe intended direction and target timing, not a guarantee
|
|
that a feature or release will ship on a particular date. Security, quality,
|
|
compatibility, and contributor availability can change priorities.
|
|
|
|
## Changing the roadmap
|
|
|
|
Anyone may propose a roadmap item or priority change through a public
|
|
[Higress issue](https://github.com/higress-group/higress/issues) or
|
|
[discussion](https://github.com/higress-group/higress/discussions). A proposal
|
|
should describe the user problem, expected outcome, project scope, major
|
|
dependencies, compatibility or security impact, and a responsible contributor
|
|
or maintainer when known.
|
|
|
|
Maintainers decide roadmap changes through the public lazy-consensus process in
|
|
[`GOVERNANCE.md`](./GOVERNANCE.md). Accepted changes are reflected in the
|
|
version-controlled website roadmap. Significant changes should link back to
|
|
the public issue, discussion, or pull request that records their rationale.
|
|
|
|
The roadmap is reviewed when planning a minor or major release and whenever a
|
|
material project-direction change is accepted. Completed work is documented in
|
|
[GitHub releases](https://github.com/higress-group/higress/releases) and the
|
|
[`release-notes`](./release-notes) directory.
|