https://bugzilla.redhat.com/show_bug.cgi?id=1122577
--- Comment #6 from Christopher Meng <[email protected]> --- (In reply to Lukas Zapletal from comment #5) > 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). Yes, and I often see this kind of "fine" tags in projects relating to RH. > 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). Yes, and then the Source tag comes without fill link. https://fedoraproject.org/wiki/Packaging:SourceURL > 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. Up to you. -- 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 [email protected] https://admin.fedoraproject.org/mailman/listinfo/package-review
