We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Let's use this issue to outline the required steps needed for us to tag a beta release for Zebra:
In critical path order, earliest tickets first. (And in dependency order, tickets with no dependencies on the left.)
impl Default for Storage
AlreadyInChain
These tickets need discussion or triage before they are implemented:
The text was updated successfully, but these errors were encountered:
Suggestion: Nice to have: #1400 ?
Sorry, something went wrong.
I've created #2870, not sure where it fits (nice to have?)
Beta release is tagged, closing this tracking issue.
We should still keep an eye on the following issues:
No branches or pull requests
Let's use this issue to outline the required steps needed for us to tag a beta release for Zebra:
Documentation
Nice to have
Security
In critical path order, earliest tickets first.
(And in dependency order, tickets with no dependencies on the left.)
Open Connections
Connection Rate
Initial Connections
Mempool
impl Default for Storage
(not a beta blocker)Performance
AlreadyInChain
errors in the syncer #2883Nice to have
Needs Triage
These tickets need discussion or triage before they are implemented:
Logging
Needs a DevOps Person
The text was updated successfully, but these errors were encountered: