dapr
/
community
mirror of https://github.com/dapr/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release-process.md 

Signed-off-by: nyemade-uversky <55847877+nyemade-uversky@users.noreply.github.com>
This commit is contained in:
nyemade-uversky 2022-10-14 11:05:32 -06:00 committed by GitHub
parent c1ff680dd1
commit 0f6db5a250
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
release-process.md
View File

@ -2,7 +2,7 @@
The Dapr project aims to release four updates in a yearly time period, typically one in each quarter (every 3 months). For example in 2022 the minor releases were Jan (1.6.0), April (1.7.0), July (1.8.0), Oct (1.9.0) and the same is expected for 2023.
<img src="Images/release-cycle-diagram.png?raw=true">
<img src="images/release-cycle-diagram.png?raw=true">
This cadence provides a balance between regular feature releases and bug fixes, giving end users time to adopt a release and providing contributors clarity on releases they can contribute towards. By having a regular “train” of releases end users and contributors can plan ahead.
@ -18,7 +18,7 @@ Each release goes through three phases in a 13 week (3 month) period.
- Stabilization and release (~ 2 weeks)
<img src="Images/feature-definition-diagram.png?raw=true">
<img src="images/feature-definition-diagram.png?raw=true">
Most significant features take at least 2 releases to become included in a release, and through the preview feature process often more. Therefore as a release comes to a close, it is not unusual to move a complex feature to the next milestone to give it time to complete the requirements of the feature lifecycle.