On Fri, 2019-09-27 at 00:20 +0200, Dan Čermák wrote: > Randy Barlow <bowlofeggs@xxxxxxxxxxxxxxxxx> writes: > > > This suggestion gives a nice clean place to write the bodhi update > > description, right in git. The commit messages can remain the way they > > are today: authored for the audience of spec file contributors. > > > > We could also support special syntax in the tag message to allow people > > to specify the various bodhi update fields (severity, karma > > requirements, whatever else) if they want to do that that way. > > I *really* like this idea, as one could still push multiple > "development" commits to git, but until one tags something, nothing is > built & released. And there is even at least one precendent, where Git tags are used to trigger some process - the GitHub releases, that list all tags & provide archives for them. So it seems like a sensible & already proven idea. > _______________________________________________ > 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 _______________________________________________ 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
