Skip to content

Commit b6e5dfb

Browse files
authored
Introduce Feature status page (#75)
* Introduce Feature status page * Updates
1 parent bf474e2 commit b6e5dfb

File tree

2 files changed

+14
-0
lines changed

2 files changed

+14
-0
lines changed

mint.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -425,6 +425,7 @@
425425
},
426426
"resources/troubleshooting",
427427
"resources/performance-and-limits",
428+
"resources/feature-status",
428429
"resources/supported-hardware",
429430
"resources/faq",
430431
"resources/release-notes",

resources/feature-status.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: "Feature Status"
3+
description: "PowerSync feature states and their implications for factors such as API stability and support."
4+
---
5+
6+
Features in PowerSync are introduced through a phased release cycle to ensure quality and stability. Below is an overview of the four release stages namely Closed Alpha, Open Alpha, Beta and Stable:
7+
8+
| **Stage** | **Production Readiness** | **API Stability** | **Support** | **Documentation** |
9+
|--------------------|-----------------------------------------------|-----------------------------------------|--------------------------|-----------------------------------------|
10+
| **Closed Alpha** | Not production-ready; purpose is early feedback and testing of new ideas. | Subject to breaking changes. | Not covered under SLAs. | Limited or placeholder documentation. |
11+
| **Open Alpha** | Not production-ready; purpose is broader testing and wider public feedback. | Subject to changes based on feedback. | Not covered under SLAs. | Basic documentation provided. |
12+
| **Beta** | Production-ready for tested use cases. | Fully stable; breaking changes clearly communicated. | Covered under SLAs. | Documentation provided; may contain known gaps. |
13+
| **Stable** | Production-ready for all main use cases. | Fully stable; breaking changes clearly communicated and backward compatibility. | Covered under SLAs. | Comprehensive and finalized documentation. |

0 commit comments

Comments
 (0)