Måns, Generally, I really appreciate your eagerness for perfection, but at this point, I really think you are overdoing it. Obviously, everying, including version.sh can be improved. OTOH and espcially in open source projects involving volunteers, workflows must also match to the way the involved people work.
As a compromise, let me bring up a variant of a proposal I made earlier this month: - tag the branchpoint 'b0.7' (b == branchpoint) - create a new branch 'release/0.7' - commit the VERSION and RELEASE files to this branch - tag the first release as 'v0.7' (v == version) Effects: - the tags starting with 'v' represent exactly what end up in the tarballs - the version numbers of master continue to increase: git-b0.7-1-gdeadaffe, ... git-b0.7-50-gdeadbeef, git-b0.7-100-gaffeaffe, etc. Would this address your concerns? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
