> You wrote: "- Each release of "galvani" should have a git tag". Does > that mean, that every file in the release should have a tag "v_0.34" > or similar?
Tags apply to the whole repository, not to individual files. I'm still confused, though. Are you the author of this software? Is there version control somewhere? You're packaging version 0.34; is there a version 0.33? Where is it? What are the differences between the two? What about version 0.35? Is it going to be developed? Where are those commits going to go? I'm guessing your development happens in some non-public place, and this is the first public releaes. Is there a non-public version control? or a non-public place to download this software? If so, can that version control (or the release tarballs) be made public as well? I think there are some (mostly older) Debian packages where upstream develops behind closed doors, and releases a tarball to the public periodically. It's unideal, but you can do that too, if that's what you want. Whatever we're doing, there has to be a clear idea of where upstream lives. Sorry to be a pain, you're just trying to do something nonstandard, and I don't know what specifically to suggest, yet.
