Michael Cronenworth <mike(a)cchtml.com> writes:
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 ...
100% agree with this and add one to two fedpkg switch-branch commands to
that with a bunch of git merge and git cherry-pick.
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
Afaik there was the good idea to use annotated git tags for that. Thus
this whole thing would be condensed to:
git commit -m $commit_msg
git tag -a -m $update_msg
fedpkg push
(-> build is run and a bodhi update is triggered)
Cheers,
Dan