-
Notifications
You must be signed in to change notification settings - Fork 773
feature: update the roadmap for a new stage #831
Conversation
3bce4a3
to
1951c09
Compare
Signed-off-by: Starnop <[email protected]>
1951c09
to
f13417b
Compare
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
==========================================
- Coverage 40.03% 40.02% -0.02%
==========================================
Files 108 108
Lines 6359 6359
==========================================
- Hits 2546 2545 -1
Misses 3606 3606
- Partials 207 208 +1
Continue to review full report at Codecov.
|
@allencloud @lowzj PTAL. THX> |
LGTM |
1 similar comment
LGTM |
|
||
## Future | ||
This is a stable version in GA stage. And we will focus on making `Dragonfly` support more scenarios. Including: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume when we say GA, it means there is no user impact going forward: no behavior change, features are not going to be deprecated, etc.
I feel somehow, we should track all the features stage, not all of them can go GA at the same time. For example, the core itself might be pretty stable, but the plugin framework might still be in alpha.
feature: update the roadmap for a new stage
feature: update the roadmap for a new stage
Signed-off-by: Gaius <[email protected]>
Signed-off-by: Starnop [email protected]
Ⅰ. Describe what this PR did
The
Dragonfly
was written with a unified programming language now and it has entered a new stage. So we need to redefine the roadmap to do some new plan for Dragonfly.Ⅱ. Does this pull request fix one issue?
None.
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
None.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews