search

ComputationalCryoEM / ASPIRE-Python

Algorithms for Single Particle Reconstruction
http://spr.math.princeton.edu
GNU General Public License v3.0
46 stars 21 forks source link

Versioning/tagging #198

Closed garrettwrong closed 3 years ago

garrettwrong commented 4 years ago

in relation to master (and CI). I see there is a version existing. I might suggest we can use something like bumpversion and document it in some sort of developer notes w.r.t handling of master branch.

We discussed this a little in the developer meetings and guidelines.

It should be pretty minor to update everything existing to work with bumpversion.

Not really any sort of priority, but I'd like to see us start doing this on the next master merge, if only just for practice.

janden commented 4 years ago

So, if I understand correctly, we would run this (it would run as part of CI) whenever we do a merge to master (from devel). We would decide at merge time whether the changes constituted a major, minor, or patch bump. That makes sense.

I guess the need for this tool is that the version is encoded in many places, so this would take care of all of them at once?

garrettwrong commented 4 years ago

Yes, it updates all known occurrences in a systematic way. It even makes the git commit for you. Its easy; I'll be happy to document it when the time comes.

janden commented 4 years ago

Ok sounds good.

garrettwrong commented 3 years ago

Closed by 272.