Roadmap: evolve Backstage into a Forgejo developer platform #31
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/backstage#31
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Provide a reliable place to discover repositories, understand services and APIs, read documentation, create projects, and inspect delivery status. Make the catalog trustworthy, add useful developer workflows, then make the platform safe to host.
Phase 1 — Trustworthy foundation
Phase 2 — Useful developer workflows
Phase 3 — Hosting readiness
Sequencing and decisions
Backlog conventions
Each delivery issue contains its own acceptance criteria. Use this issue for overview and sequencing decisions, not duplicate task details. Native Forgejo issue dependencies capture mandatory gates. The three phases are documented here; no milestones were created because milestone creation is not exposed by the available Forgejo tools.
Existing work
Keep Renovate's Dependency Dashboard #8 as the source of dependency PRs, rather than duplicating individual upgrades. Current automated-review failures are distinct from application validation failures.
Initially out of scope