From 34f90e6b3079a81720209d8fed4e9c93fb890884 Mon Sep 17 00:00:00 2001 From: blam Date: Tue, 14 Feb 2023 17:32:38 +0100 Subject: [PATCH] chore: fixing release notes and removing link from todo Signed-off-by: blam --- docs/releases/v1.11.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releases/v1.11.0.md b/docs/releases/v1.11.0.md index da33e65ff0..e385bfead5 100644 --- a/docs/releases/v1.11.0.md +++ b/docs/releases/v1.11.0.md @@ -20,7 +20,7 @@ We’d love to hear if you have any issues when testing the new version, please The [new Backend System](https://backstage.io/docs/backend-system/) is now in alpha. We encourage plugin owners to try out the new system by adding support for it in their plugin backends, but we do not yet recommend migrating over to using this new system for production backend deployments. -This new system aims to greatly simplify the setup and wiring of Backstage backends. It formalizes and simplifies how common services and plugins are installed and interact with each other, and restructures both plugins and backends to make them much easier to maintain. To read more about this new system and how it came about, check out our [blog post](#TODO) on the topic. +This new system aims to greatly simplify the setup and wiring of Backstage backends. It formalizes and simplifies how common services and plugins are installed and interact with each other, and restructures both plugins and backends to make them much easier to maintain. The documentation starts [here](https://backstage.io/docs/backend-system/). Migration guides exist to help you get your [backend](https://backstage.io/docs/backend-system/building-backends/migrating) and [plugins](https://backstage.io/docs/backend-system/building-plugins-and-modules/migrating) migrated, but you don’t have to do it all in one go - the path forward can be incremental.