<snip>
> Well, if you don't push the tag and you do a build, you will get N-V-R
> like foo-1.0-1.git.3.abcdef12. E.g. it won't be a clean N-V-R because
I meant "I.e." there, not "E.g."...just to be clear.
> it doesn't come from a tagged commit. If you push a tag and repeat a
> build from that same commit (or from that tag, see above), you will
> now get a clean N-V-R like foo-1.0-2. This is assuming Release: {{{
> git_dir_release }}} is used in the spec file to enable the automatic
> generation of release. The annotated tags represent releases. if you
> build an unreleased commit, you get a "work-in-progress" N-V-R and
> also changelog won't be populated with the latest changes. This
> workflow needs "pushing a tag" to be a build trigger so that it is
> convenient.
>
> Best regards
> clime
>
> >
> > Thanks,
> > Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
