Fredrik Adelöw
8.5 KiB
id, title, description
| id | title | description |
|---|---|---|
| roadmap | Roadmap | Roadmap of Backstage |
The Backstage Roadmap
Backstage is currently under rapid development. This page details the project’s public roadmap, the result of ongoing collaboration between the core maintainers and the broader Backstage community. Treat the roadmap as an ever-evolving guide to keep us aligned as a community on:
- Upcoming enhancements and benefits,
- Planning contributions and support,
- Planning the project’s adoption,
- Understanding what things are coming soon,
- Avoiding duplication of work
How to influence the roadmap
As we evolve Backstage, we want you to contribute actively in the journey to define the most effective developer experience in the world.
A roadmap is only useful if it captures real needs. If you have success stories, feedback, or ideas, we want to hear from you! If you plan to work (or are already working) on a new or existing feature, please let us know, so that we can update the roadmap accordingly. We are also happy to share knowledge and context that will help your feature land successfully.
You can also head over to the CONTRIBUTING guidelines to get started.
If you have specific questions about the roadmap, please create an issue, ping us on Discord, or book time with the Spotify team.
How to read the roadmap
The Backstage roadmap lays out both “what’s next” and “future work”. With "next" we mean features planned for release within the ongoing quarter from January through March 2022. With "future" we mean features in the radar, but not yet scheduled.
The long-term roadmap (12 - 36 months) is not detailed in the public roadmap. Third-party contributions are also not currently included in the roadmap. Let us know about any ongoing developments and we’re happy to include it here as well.
Roadmap evolution
Will this roadmap change? Obviously!
Roadmap are always evolving and ours is no different; you can expect to see this updated roughly every month.
What’s next
The feature set below is planned for the ongoing quarter, and grouped by theme. The list order doesn’t necessarily reflect priority, and the development/release cycle will vary based on maintainer schedules.
Backstage 1.0 (and following versions)
During the first quarter of 2022, we plan to finalize and release version 1.0 of the Backstage platform (defined by the Core, Catalog, Scaffolder and TechDocs). Included as part of this milestone:
- Deciding on the cadence of minor/weekly/daily releases to provide clarity on the frequency and expectations for future versions of the platform and its defining modules.
- Establish the support model to set the expectations from the adopters in their respective use cases.
Backstage Security Audit
This initiative is the first of a broader Security Strategy for Backstage. The purpose of the Security Audit is to involve third-party companies in auditing the platform and highlighting potential vulnerabilities. The benefit for the adopters is clear: We want Backstage to be as secure as possible, and we want to make it reliable through a specific initiative. This initiative in particular is done together, and with the support of, the Cloud Native Computing Foundation (CNCF).
Moving to Incubation in CNCF
The progress of the request can be seen here.
Future work
The following feature list doesn’t represent a commitment to develop, and the list order doesn’t reflect any priority or importance, but these features are on the maintainers’ radar, with clear interest expressed by the community.
- Backend Services: To better scale and maintain the Backstage instances, a backend layer of services is planned to be introduced as part of the software architecture. This layer of backend services will help in decoupling the various modules (e.g. Catalog and Scaffolder) from the frontend experience.
- Security Plan (and Strategy): The purpose of the Security Strategy is to move another step along the path to maturing the platform, setting the expectations of any adopters from a security standpoint.
- Search GA:.
- GraphQL support: Introduce the ability to query Backstage backend services with a standard query language for APIs.
- Telemetry: To efficiently generate logging and metrics in such a way that adopters can get insights so that Backstage can be monitored and improved.
- Improved UX design: Provide a better Backstage user experience through visual guidelines and templates, especially navigation across plug-ins and portal functionalities.
Completed milestones
Read more about the completed (and released) features for reference.
-
CI plugins: CircleCI, Jenkins, GitHub Actions and TravisCI
-
Backstage Software Catalog can read from: GitHub, GitLab, Bitbucket
-
Support auth providers: Google, Okta, GitHub, GitLab, auth0, AWS
-
CI plugins: CircleCI, Jenkins, GitHub Actions and TravisCI
-
Backstage Software Catalog can read from: GitHub, GitLab, Bitbucket
-
Support auth providers: Google, Okta, GitHub, GitLab, auth0, AWS