Add docs on unstable release process (#13015)

Author: brophdawg11

docs/community/api-development-strategy.md

@@ -30,6 +30,8 @@ Unstable flags are not recommended for production:
 
 When you opt-in to an unstable flag you are becoming a contributor to the project, rather than a user. We appreciate your help, but please be aware of the new role!
 
+Because unstable flags are experimental and not guaranteed to stick around, we ship them in SemVer patch releases because they're not new _stable_/_documented_ APIs. When an unstable flag stabilizes into a Future Flag, that will be released in a SemVer minor release and will be properly documented and added to the [Future Flags Guide](../upgrading/future).
+
 To learn about current unstable flags, keep an eye on the [CHANGELOG](../start/changelog).
 
 ### Example New Feature Flow

docs/upgrading/future.md

@@ -0,0 +1,11 @@
+---
+title: Future Flags
+---
+
+# Future Flags and Deprecations
+
+This guide walks you through the process of adopting future flags in your React Router app. By following this strategy, you will be able to upgrade to the next major version of React Router with minimal changes. To read more about future flags see [API Development Strategy](../community/api-development-strategy).
+
+We highly recommend you make a commit after each step and ship it instead of doing everything all at once. Most flags can be adopted in any order, with exceptions noted below.
+
+<docs-warning>**There are no current future flags in React Router v7**</docs-warning>