mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-10-22 06:13:00 +00:00
Shubham Pampattiwar
f8c23ef4e0
Adds ARCHITECTURE.md as a high-level, discoverable entry point to Velero's architecture, goals, and use cases that links to velero.io and the design/ directory instead of duplicating content. Expands ROADMAP.md from a single wiki link (which pointed at the stale vmware-tanzu path) into a short description of how the roadmap is maintained, and repoints the wiki link to velero-io. Links ARCHITECTURE.md from the README so it is easy to find. These docs address incubation-review feedback that Velero's goals, architecture, and roadmap process were scattered across the website. Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>
1.0 KiB
1.0 KiB
Velero Roadmap
Velero maintains its roadmap in the project wiki. The wiki holds the current roadmap, archived roadmaps from previous release cycles, and guidance on how roadmap items are proposed and prioritized.
How the roadmap is maintained
Roadmap items are driven by the community and the maintainers:
- Larger features start as a design proposal in the
design/directory, followingdesign/_template.md. Proposals are discussed on the pull request and in the community meetings before they are accepted. - Feature requests and bugs are tracked as GitHub issues.
- Priorities are reviewed by the maintainers each release cycle and discussed in the bi-weekly community meetings, which are open to everyone.
Anyone can propose a roadmap item by opening an issue or a design proposal, or by raising it in a community meeting.