include git branch name in the --version[-and-path] output #1953

Closed
opened 2013-04-24 13:58:07 +00:00 by daira · 3 comments
daira commented 2013-04-24 13:58:07 +00:00
Owner

The linear versioning of the Tahoe code makes it difficult to distinguish branches (such as the I2P branch or the cloud backend branch). In /tahoe-lafs/trac-2024-07-25/issues/9414#comment:132995 Zooko suggests to change the appname in the I2P branch, but that falls foul of #1159. It also depends on branch maintainers to remember to do the right thing, which is quite inconvenient given that the code needs to be patched to change the appname. If tahoe --version[-and-path] (and the version info on the Welcome page) showed the git branch name, that would be much better I think.

The linear versioning of the Tahoe code makes it difficult to distinguish branches (such as the I2P branch or the cloud backend branch). In [/tahoe-lafs/trac-2024-07-25/issues/9414](/tahoe-lafs/trac-2024-07-25/issues/9414)#[comment:132995](/tahoe-lafs/trac-2024-07-25/issues/1953#issuecomment-132995) Zooko suggests to change the appname in the I2P branch, but that falls foul of #1159. It also depends on branch maintainers to remember to do the right thing, which is quite inconvenient given that the code needs to be patched to change the appname. If `tahoe --version[-and-path]` (and the version info on the Welcome page) showed the git branch name, that would be much better I think.
tahoe-lafs added the
code
normal
defect
1.10a2
labels 2013-04-24 13:58:07 +00:00
tahoe-lafs added this to the soon milestone 2013-04-24 13:58:07 +00:00
daira commented 2013-04-24 15:32:25 +00:00
Author
Owner
Please review: <https://github.com/tahoe-lafs/tahoe-lafs/commit/1953-branch-in-version>.
warner commented 2013-04-24 22:46:51 +00:00
Author
Owner

I made one comment on that patch, but otherwise it seems good. I don't want to add it to 1.10, though, feels slightly risky this late in the process.

I made one comment on that patch, but otherwise it seems good. I don't want to add it to 1.10, though, feels slightly risky this late in the process.
tahoe-lafs modified the milestone from soon to 1.11.0 2013-04-24 22:46:51 +00:00
Daira Hopwood <david-sarah@jacaranda.org> commented 2013-05-01 21:39:53 +00:00
Author
Owner

In changeset:8a1b2c7aa6f10882:

Show git branch in version output. fixes #1953
Also make sure strings in _version.py are correctly escaped, and repair a test.

Signed-off-by: Daira Hopwood <david-sarah@jacaranda.org>
In changeset:8a1b2c7aa6f10882: ``` Show git branch in version output. fixes #1953 Also make sure strings in _version.py are correctly escaped, and repair a test. Signed-off-by: Daira Hopwood <david-sarah@jacaranda.org> ```
tahoe-lafs added the
fixed
label 2013-05-01 21:39:53 +00:00
Daira Hopwood <david-sarah@jacaranda.org> closed this issue 2013-05-01 21:39:53 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1953
No description provided.