On 12/02/2016 10:14 AM, Andrew Savchenko wrote: > > If both policies are to be followed, users will see something like: > foo-1.0 -> foo-1.1-r8 (assuming each sufficient change was made as > a separate commit with a revision bump). > > While such versioning change is technically correct, it is > confusing for our users and makes future maintainance harder, > because of multiple file renames (yeah, I know about git diff > --find-renames, but this kludge is not perfect).
Do you have a situation in mind where going from -r0 to -r8 in one `git push` is a problem? What maintenance becomes harder? I can see how it could be confusing, but only in the sense that we've been doing it wrong for so long that now it's surprising to see it done right. Now it makes sense: the -r8 version contains 8 more fixes than -r0. I should be able to `git checkout` any commit in the repo and have the tree not be broken. Your proposal eliminates that guarantee, and the bar for doing so should be high, I think.
