On 12/15/20 4:29 PM, Miroslav Suchý wrote:
What you - as Fedora packager - find most time consuming on packaging?
Where you will welcome more simplicity or automation?
Pushing updates requires too many steps, IMHO.
1. <make edits>
2. fedpkg mockbuild
3. <make edits>
4. fedpkg commit -p
5. fedpkg build
6. fedpkg update ...
Can we make the Bodhi update notes part of the git repo? Ex. ChangeLog.md
If not, could a file be referenced instead of a "--notes" argument? Ex. --notes-file
ChangeLog.md
Stretch goal: Bodhi update defaults (inc. notes?) as part of git, too. Ex. update.yml
Step 4 could then become the final step:
fedpkg commit -p -b -u
(-b = build, -u = send update if build is successful)
Regards,
Michael
_______________________________________________
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
