-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up #69
Clean up #69
Conversation
Signed-off-by: Xiaolong Fu <[email protected]>
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.
Why archiving the code?
We are planning to refactor Dagrs using the flow-based programming paradigm. Our plan is as follows |
And we also provide a brief introduction about our plan in docs/upgrade.md |
I think it's better to do this in a temporary |
I am a fan of trunk-base development, and I hope to rewrite dagrs from the beginning and cross-review each PR to help the engine have better code quality. |
So if you don't wanna keep the original code in main and start a new branch, why not just remove the current code. Why move them? |
No description provided.