https://bugzilla.redhat.com/show_bug.cgi?id=1122577 --- Comment #5 from Lukas Zapletal <lzap@xxxxxxxxxx> --- Chris, my tag is fine, I use tito tool (https://github.com/dgoodwin/tito) which is configured by default to store RELEASE in tags and I want to do that, because it is _very_ helpful to track whole nvre as tags. Tito has mechanisms to check for pushed tags when submitting builds into Koji (or making release tarballs), because the SPEC file is part of the upstream project in this case. This is how it works and there are many other projects with the similar approach (e.g. Spacewalk - https://git.fedorahosted.org/cgit/spacewalk.git/refs/tags). It is not confusing if you realize that the SPEC file is part of the upstream project, I will be the Fedora maintainer. Other distribution maintainers can safely ignore the release, it is only used to fix bugs in the Fedora packaging. The tito tool is capable of making _correct_ tarballs (/tmp/tito/git-xcleaner-1.1.tar.gz in my case). I have never intended to use github.com tarball feature for the reason I've described above. Therefore I will add this as Source URL: http://lzap.fedorapeople.org/projects/git-xcleaner/git-xcleaner-1.1.tar.gz My versioning convention will be 1.1234, because this tiny tool is not worth three levels in versioning scheme. To be honeste, I like simple number versioning scheme (e.g. Google Chrome or systemd), but I am fine with the standard two levels. Since I had one upstream change (changed welcome text), I released new version 1.2 which contains this change plus the new URL upstream tarball site: http://lzap.fedorapeople.org/fedora-packaging/git-xcleaner/1.2-1/ -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review