Replies: 1 comment
|
@rahst12 thanks for the callout here, we've been focused on other repos, but we will prioritize getting these PRs reviewed, and incorporated if relevant. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Ratel remains one of the primary entry points and visual interfaces for developers exploring and managing Dgraph clusters. Over the past 6 months, the community has submitted valuable pull requests addressing core UX friction, modern DQL syntax compatibility, dependency updates, and bug fixes.
However, open pull requests have faced review delays and stagnation due to diverging branches and stale code.
As the community looks to these ratel features, how should these be handled?
One option: should there be an upstream fork to help test and integrate prior to product integration?
All reactions