move to Versioneer for git-based version-string generation #2748

Open
opened 2016-03-22 04:32:56 +00:00 by warner · 4 comments

(I thought we had this ticketed already, but couldn't find it just now)

We have code in setup.py to run git describe to figure out what version string to use. This allows us to make a release by doing "git tag", without needing to manually update a file each time.

I wrote a system called Versioneer to do this. It works under py2 and py3, and handles git checkouts, sdist tarballs, setup.py install, git archive tarballs, and more.

We should remove our custom setup.py code and switch to Versioneer.

(I thought we had this ticketed already, but couldn't find it just now) We have code in `setup.py` to run `git describe` to figure out what version string to use. This allows us to make a release by doing "git tag", without needing to manually update a file each time. I wrote a system called [Versioneer](https://github.com/warner/versioneer) to do this. It works under py2 and py3, and handles git checkouts, sdist tarballs, `setup.py install`, `git archive` tarballs, and more. We should remove our custom `setup.py` code and switch to Versioneer.
warner added the
packaging
normal
task
1.10.2
labels 2016-03-22 04:32:56 +00:00
warner added this to the 1.11.0 milestone 2016-03-22 04:32:56 +00:00
warner self-assigned this 2016-03-22 04:32:56 +00:00
Author

Milestone renamed

Milestone renamed
warner modified the milestone from 1.11.0 to 1.12.0 2016-03-22 05:02:52 +00:00
Author

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
warner modified the milestone from 1.12.0 to 1.13.0 2016-06-28 18:20:37 +00:00

Moving open issues out of closed milestones.

Moving open issues out of closed milestones.
exarkun modified the milestone from 1.13.0 to 1.15.0 2020-06-30 14:45:13 +00:00
Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
meejah modified the milestone from 1.15.0 to soon 2021-03-30 18:40:19 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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