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
document how to use the bug tracker (including for release triaging) #7236
Comments
Comment author: @hcarty It would be very nice to have a prominent link that takes you directly to the list of bugs assigned to the next release. That would avoid the need to explain "how to search mantis" to someone who wants to help with higher priority (from a release standpoint) issues. |
Comment author: junsli @hcarty: I think that is what the Roadmap link in heading for, isn't it? |
Comment author: @hcarty Thanks for pointing me to that, I didn't realize that's what it was! Which somewhat illustrates my point: it would be nice to have a link directly to that view of mantis from CONTRIBUTING.md. |
Comment author: @hcarty Another nice link to include would be http://caml.inria.fr/mantis/search.php?project_id=1&sticky_issues=1&sortby=last_updated&dir=DESC&highlight_changed=24&hide_status_id=90&tag_string=junior_job listing all of the junior_job-tagged tickets (courtesy of the OCaml Labs compiler hacking page). |
@gasche Shall we close this? |
Well I think we should still document how we use the Github bug tracker. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Original bug ID: 7236
Reporter: @gasche
Status: acknowledged (set by @gasche on 2016-04-20T15:35:52Z)
Resolution: open
Priority: low
Severity: feature
Target version: 4.07.0+dev/beta2/rc1/rc2
Category: documentation
Monitored by: runhang @hcarty
Bug description
There are many tips that we could provide to our users about how to use the bug tracker, for example in the CONTRIBUTING.md document. Some useful information would be:
-- suggesting "related" bugs
-- how to filter for bugs to solve or triage before the next release,
what kind of triaging works helps accelerate the release process
The text was updated successfully, but these errors were encountered: