Skip to content
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

[Tracking Issue] Database layer performance and stability #1172

Closed
5 of 7 tasks
daniel-farina opened this issue Mar 29, 2022 · 2 comments
Closed
5 of 7 tasks

[Tracking Issue] Database layer performance and stability #1172

daniel-farina opened this issue Mar 29, 2022 · 2 comments

Comments

@p0mvn
Copy link
Member

p0mvn commented Mar 29, 2022

How is this different from the epic?

Is it for low-priority items to be backlogged for the future?

@ValarDragon
Copy link
Member

Sorry for the late reply, yeah thats exactly it! Wanted to get peoples thoughts on keeping epics just to the components we want to get done in a certain frame, and then keeping indexes on backlog items in these tracking issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

3 participants