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

Bug reporting instructions should be more helpful #31

Open
bklang opened this issue Jun 24, 2014 · 1 comment
Open

Bug reporting instructions should be more helpful #31

bklang opened this issue Jun 24, 2014 · 1 comment

Comments

@bklang
Copy link
Member

bklang commented Jun 24, 2014

There are a couple of suggestions that could do with explanation:

  • If we ask how to enable trace logging, we should explain how, or link to an explanation how
  • Instead of asking for exact version numbers, just require the Gemfile.lock and the Ruby version
  • The suggestions for good bug reporting should be visually separated so it doesn't appear that they are part of the actual bug report
  • Do we want to additionally ask for Asterisk or FS logs? Or do we wait until they are necessary?
@benlangfeld
Copy link
Member

Instead of asking for exact version numbers, just require the Gemfile.lock and the Ruby version

We ask for full trace logs from startup. These include these values.

Do we want to additionally ask for Asterisk or FS logs? Or do we wait until they are necessary?

They're always helpful.

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

No branches or pull requests

2 participants