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

Include identifying version number #31

Open
mikldt opened this issue Nov 9, 2015 · 1 comment
Open

Include identifying version number #31

mikldt opened this issue Nov 9, 2015 · 1 comment

Comments

@mikldt
Copy link
Member

mikldt commented Nov 9, 2015

We should make it possible to figure out which version of the player is running to help diagnose problems. This could be as simple as a file somehwere.

This could optionally be reported back to the server via bandshell.

We should also create git tags with each new release to help trace files back to the code. A good resolution to this would be a release handbook (or automated script) which includes both updating the version internally and tagging the release.

@augustf
Copy link
Member

augustf commented Nov 9, 2015

Well, the 0.9.x numbering scheme is more or less of my invention. But in this case, what are we showing and tagging? The bandshell release, the player build? What if someone does a gem update on bandshell? Do we just show the version of each?

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