On Tue, Apr 7, 2020 at 3:46 AM Vít Ondruch <vondruch(a)redhat.com> wrote:
...
> * Added a section explaining how we will deal with side-tags
Thank you for addressing this.
However, could you please elaborate what will be the actual trigger to
do rebuild of some package in ELN? It can't be `git push` if you take
side-tags into account. So will it be tagging into 'rawhide' (f33 ATM)?
Will it be mixture? How are you going to determine what is the
appropriate commit hash? You possibly don't know yet ...
I need to investigate how much of it will be net-new work, but we
intend to rely on fedora-messaging notifications to trigger the
rebuilds. Tagging into F33 is probably our best bet; we do actually
have the ability to query Koji for which commit hash was used to run
the build, so we can rely on that. The exact mechanism here is TBD,
but I wanted to make sure the intent of the design was covered in the
Change Proposal.