Skip to content
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

Closed
vicuna opened this issue Apr 20, 2016 · 7 comments
Closed

document how to use the bug tracker (including for release triaging) #7236

vicuna opened this issue Apr 20, 2016 · 7 comments

Comments

@vicuna
Copy link

vicuna commented Apr 20, 2016

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:

  • how to search for similar bugs (I use google "site:caml.inria.fr/mantis" and it's surprisingly effective)
  • how to choose a reporting category or Target version
  • how to contribute if they want to help triaging:
    -- 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
@vicuna
Copy link
Author

vicuna commented Apr 20, 2016

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.

@vicuna
Copy link
Author

vicuna commented Apr 21, 2016

Comment author: junsli

@hcarty: I think that is what the Roadmap link in heading for, isn't it?

@vicuna
Copy link
Author

vicuna commented Apr 21, 2016

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.

@vicuna
Copy link
Author

vicuna commented Apr 21, 2016

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).

@vicuna vicuna added this to the 4.07.0 milestone Mar 14, 2019
@mshinwell
Copy link
Contributor

@gasche Shall we close this?

@gasche
Copy link
Member

gasche commented Mar 18, 2019

Well I think we should still document how we use the Github bug tracker.

@gasche gasche changed the title document how to use Mantis (including for release triaging) document how to use the bug tracker (including for release triaging) Mar 18, 2019
@github-actions
Copy link

github-actions bot commented May 9, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants