Labels
Labels
106 labels
- Issues resulting from a code or process audit
- Work that needs to be done sometime in the future. No milestone assigned or not yet available.
- Tickets pertaining to the base configuration library
- Tickets pertaining to the base crypto library
- Tickets pertaining to the base logging library
- Tickets pertaining to the base metrics library
- Tickets pertaining to the base resource management library
- Issues related to the Block Node.
- All Issues related to block streams
- Further development work cannot be done.
- An error that causes the feature to behave differently than what was expected based on design.
- Issue/PR closed without resolution.
- Issue/PR was resolved (work was done/merged).
- Issue declined and will not be worked.
- Pull requests that update a dependency file
- Issue/PR for feature design documents.
- DevOps dependency, review, test and deployment.
- Pull requests that update Docker code
- Duplicates an existing issue either directly or indirectly.
- All issues related to dynamic address book
- A body of work that can be broken down into specific tasks.
- An issue found after the feature was completed, but caught in a testing env prior to a prod release.
- Issues that has been groomed
- Tickets that are Exection Team Responsibility
- Enhancing an existing feature driven by business requirements. Typically backwards compatible.