Difference between revisions of "Resources/Issue tracker"
From AtoM wiki
(Detailed instructions added.) |
|||
| (17 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Main Page]] > [[Resources]] > | + | {{#pagetitle: Issue tracker }} |
| + | [[Main Page]] > [[Resources]] > Resources/Issue tracker | ||
| − | |||
| − | + | Artefactual uses [https://github.com/artefactual/atom/issues GitHub] to track bugs and issues in AtoM. | |
| − | + | <admonition type="Important"> | |
| + | Artefactual no longer uses [https://projects.artefactual.com Redmine] for issue tracking. This has been deprecated. If you are looking for an issue from Redmine and cannot find it in GitHub, please contact [mailto:contributors@artefactual.com contributors@artefactual.com]. | ||
| + | </admonition> | ||
| − | |||
| − | + | We're currently in the process of cleaning up legacy issues from our issue list, but as we progress with this work, this is what you can expect to see: | |
| − | + | * An issue can refer to a ''feature'', a ''bug'', or a ''task''. Features are enhancements or new functionality that did not previously exist. Bugs are reports of existing functionality that does not work as expected, or problems with the application. | |
| + | * Issues are given tags. If the issue is is a bug it will generally be tagged with '''Type: Bug''' and if it is a feature or enhancement it will be tagged with '''Type: enhancement'''. | ||
| + | * An issue is given a '''milestone''' (e.g. Release 2.11) '''only''' if we are certain it will be included in an upcoming release. Bugs that are reported but not sponsored for development or fixed by Artefactual or a community contributor will be left without a milestone until they have been addressed, and can be associated with a specific release. See all milestones [https://github.com/artefactual/atom/milestones here]. | ||
| + | * Bug reports should be given a '''Tested version''' in the issue, so that we know which version of the application was used to reproduce the issue, and we can assess if a bug remains relevant to future releases over time. | ||
| − | |||
| − | + | <admonition type="Important"> | |
| + | You can find out how to submit an issue in our [https://github.com/artefactual/atom/blob/qa/2.x/CONTRIBUTING.md contributing guide]. | ||
| + | </admonition> | ||
| − | |||
| − | + | ----- | |
| − | + | * [[Resources|Back to Resources]] | |
| − | + | * [[Main Page|AtoM wiki home]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Resources]] | [[Category:Resources]] | ||
Latest revision as of 07:42, 3 July 2025
Main Page > Resources > Resources/Issue tracker
Artefactual uses GitHub to track bugs and issues in AtoM.
Important
Artefactual no longer uses Redmine for issue tracking. This has been deprecated. If you are looking for an issue from Redmine and cannot find it in GitHub, please contact contributors@artefactual.com.
We're currently in the process of cleaning up legacy issues from our issue list, but as we progress with this work, this is what you can expect to see:
- An issue can refer to a feature, a bug, or a task. Features are enhancements or new functionality that did not previously exist. Bugs are reports of existing functionality that does not work as expected, or problems with the application.
- Issues are given tags. If the issue is is a bug it will generally be tagged with Type: Bug and if it is a feature or enhancement it will be tagged with Type: enhancement.
- An issue is given a milestone (e.g. Release 2.11) only if we are certain it will be included in an upcoming release. Bugs that are reported but not sponsored for development or fixed by Artefactual or a community contributor will be left without a milestone until they have been addressed, and can be associated with a specific release. See all milestones here.
- Bug reports should be given a Tested version in the issue, so that we know which version of the application was used to reproduce the issue, and we can assess if a bug remains relevant to future releases over time.