Mattia Verga

@dependabot rebase

@dependabot rebase

@dependabot rebase

For reference, this is already in the [developer documentation](https://github.com/fedora-infra/bodhi/blob/develop/docs/developer/index.rst#contribution-guidelines).

I did a build of `dev` for Fedora Rawhide and gcc 12.2, you might be interested in some more warnings (full log [here](https://kojipkgs.fedoraproject.org//packages/rawtherapee/5.9~20221002git4059ae5/1.fc38/data/logs/x86_64/build.log): - in `rtengine/xtrans_demosaic.cc`: ``` /builddir/build/BUILD/RawTherapee-4059ae5bcad8e18443bf8f37bcff84de1dcc0d03/rtengine/procparams.cc: In member...

In the past there was some attempt to build the docs in ReadTheDocs.org, but it wasn't possible because of dependencies... now that we have separate packages, maybe we can re-try....

https://github.com/dependabot rebase

Just one waiver with null scenario: https://github.com/fedora-infra/bodhi/blob/891564724f08124c3272e2f16717b41fd9a56e78/bodhi/server/models.py#L3102-L3117

I think we could add a new email template with different instructions and use that if the update is a "new package" type. Something like: ``` -------------------------------------------------------------------------------- Fedora%(testing)s New Package...

The "Resolves: rhbz#..." thing only works for automatic updates. For normal or side-tag updates the user is supposed to manually add the bugs, since they already have to manually create...