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

IDE: 'About Bela' should be more informative #280

Open
jarmitage opened this Issue Apr 23, 2017 · 7 comments

Comments

Projects
None yet
3 participants
@jarmitage
Contributor

jarmitage commented Apr 23, 2017

Current example output:

About Bela

You are using Bela Version 0.2, October 2016. Bela is an open source project, and is a product of the Augmented Instruments Laboratory at Queen Mary University of London, and Augmented Instruments Ltd. For more information, visit http://bela.io

It would be useful if this contained e.g. Git version / branch. Or this could just be displayed at the bottom of the Project Settings window.

@giuliomoro

This comment has been minimized.

Show comment
Hide comment
@giuliomoro

giuliomoro Dec 20, 2017

Contributor

Actually the "Version" number as reported here is pretty misleading, I'd suggest we remove it (e.g.: now master can run on both v0.2 and v0.3 images). Having the git commit hash or branch is not easy to do either (that is: baking it into the source code is out of question and if the board is updated through the update_board script, then the git hash would not be updated).

Contributor

giuliomoro commented Dec 20, 2017

Actually the "Version" number as reported here is pretty misleading, I'd suggest we remove it (e.g.: now master can run on both v0.2 and v0.3 images). Having the git commit hash or branch is not easy to do either (that is: baking it into the source code is out of question and if the board is updated through the update_board script, then the git hash would not be updated).

@jarmitage

This comment has been minimized.

Show comment
Hide comment
@jarmitage

jarmitage Dec 20, 2017

Contributor

Ok. The problem that remains, that I have had in the past, is that it's impossible to tell whether an update has actually worked or not without testing random features.

Contributor

jarmitage commented Dec 20, 2017

Ok. The problem that remains, that I have had in the past, is that it's impossible to tell whether an update has actually worked or not without testing random features.

@apmcpherson

This comment has been minimized.

Show comment
Hide comment
@apmcpherson

apmcpherson Dec 20, 2017

A better solution, if possible, would be to display two version numbers: the Bela image version, and the repo version. Perhaps a simplified numbering for the latter, e.g. an incrementing number for each commit, possibly a unique letter for each branch?

apmcpherson commented Dec 20, 2017

A better solution, if possible, would be to display two version numbers: the Bela image version, and the repo version. Perhaps a simplified numbering for the latter, e.g. an incrementing number for each commit, possibly a unique letter for each branch?

@giuliomoro

This comment has been minimized.

Show comment
Hide comment
@giuliomoro

giuliomoro Dec 20, 2017

Contributor

The recommended procedure is for someone to download the zip archive and use the "update" button. Downloading the zip archive means that no git info are retained, therefore there is no way to get commit hash / branch.

Contributor

giuliomoro commented Dec 20, 2017

The recommended procedure is for someone to download the zip archive and use the "update" button. Downloading the zip archive means that no git info are retained, therefore there is no way to get commit hash / branch.

@jarmitage

This comment has been minimized.

Show comment
Hide comment
@jarmitage

jarmitage Dec 20, 2017

Contributor

Maybe the main repo can have a .json file somewhere with git / version info?

Contributor

jarmitage commented Dec 20, 2017

Maybe the main repo can have a .json file somewhere with git / version info?

@giuliomoro

This comment has been minimized.

Show comment
Hide comment
@giuliomoro

giuliomoro Dec 20, 2017

Contributor

This should be able to read image revision from /etc/motd

grep "Bela image" /etc/motd |grep -o "v[0-9]\{1,\}\.[0-9]\{1,\}\..*," | sed "s/,//"
Contributor

giuliomoro commented Dec 20, 2017

This should be able to read image revision from /etc/motd

grep "Bela image" /etc/motd |grep -o "v[0-9]\{1,\}\.[0-9]\{1,\}\..*," | sed "s/,//"
@giuliomoro

This comment has been minimized.

Show comment
Hide comment
@giuliomoro

giuliomoro Dec 20, 2017

Contributor

Having a json file somewhere means updating it.

The two options I see to have the version up to date:

  • a "build" server that downloads from github and adds in the version file.
  • built-in direct update from github!
Contributor

giuliomoro commented Dec 20, 2017

Having a json file somewhere means updating it.

The two options I see to have the version up to date:

  • a "build" server that downloads from github and adds in the version file.
  • built-in direct update from github!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment