Labels
Labels
22 labels
- Pull requests that update a dependency file
- An issue that should be easy to tackle as a first issue
- Assigned to things that are bugs, but that have not been checked
- Added to indicate that a closed issue represents a bug that has been fixed
- Indicates that a potential fix is in place and the fix needs manual testing
- Indicates that a code change, in a branch/PR, needs to be reviewed
- Should be the default status for issues that have been acknowledged, but not yet processed.
- For issues that are (critical) bugs, denotes that the bug is reproduced, but no further action taken
- Used for issues that are bug reports that cannot be reproduced
- Waiting for changes to a Pull Request
- Indicates that the person who is working on the issue needs feedback from someone else
- Waiting for an updated release of the OWL API for this issue to be resolved
- Indicated that we expect that the issue can be closed soon if no further comments are received.
- Indicates that Protege is not working as expected
- A type of bug that causes Protege to not start, not load/save ontologies, data loss etc.
- A bug that originates in the OWL API that leads to data loss etc.
- A performance issue that blocks normal reasonable use of Protege
- Any issue with the documentation rather than the software itself
- A request for a change that is an enhancement
- Indicates that an issue represents a code clean or maintenance
- A bug in the OWL API that is manifested in Protege. Should be reported on the OWL API tracker
- A performance issue