You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tool needs to write out clear information about the current version. This could be done in the same fashion as the command line that is to stdout and results.txt.
The text was updated successfully, but these errors were encountered:
Agreed. We also need to add clear versioning, see #13 . I don't have any experience with the automated versioning stuff so I need to investigate that, or I'm open to suggestions.
I'm not sure how you would do automatic versioning for something as
arbitrary as a version label. I understand this branch to be a release
branch which is updated whenever you feel like it. If you had a "live"
branch i.e. a development branch you could just use the GIT hash. I guess
you could update a file every time a check-out (pull) occurs.
For the time being you could just manually add a version tag e.g. by using
arparse's version action.
On 16 December 2015 at 19:30, David L. Mobley [email protected]
wrote:
Agreed. We also need to add clear versioning, see #13 #13 . I don't
have any experience with the automated versioning stuff so I need to
investigate that, or I'm open to suggestions.
—
Reply to this email directly or view it on GitHub #46 (comment)
.
davidlmobley
changed the title
Version information missing
Add at least some form of a version tag to be printed to stdout and results.txt
Dec 22, 2015
The tool needs to write out clear information about the current version. This could be done in the same fashion as the command line that is to stdout and results.txt.
The text was updated successfully, but these errors were encountered: