Hi, Guillaume Le Vaillant <g...@posteo.net> writes:
> Maxim Cournoyer <maxim.courno...@gmail.com> skribis: > >> Hi, >> >> Guillaume Le Vaillant <g...@posteo.net> writes: >> >>> Lars-Dominik Braun <l...@6xq.net> skribis: >>> >>>> Hi, >>>> >>>> it seems the core-updates branch is first in the merge-queue. haskell-team >>>> was successfully built by the CI and is ready to be merged. Since there >>>> does not seem to be an ETA for core-updates, can I skip the queue and >>>> go ahead with merging haskell-team? >>>> >>>> Lars >>> >>> Hi. >>> The lisp-team branch is also in a good shape and ready to be merged. >> >> I think it's fine to merge these first; perhaps the core-updates merge >> request should be removed if it was preposterous (usually we issue the >> merge request when we are confident the branch is ready to me merged). > > Hi. > > It might be more logical to have two steps. First a "work started on > xyz-team branch" message to indicate to the QA to make the stats for > this branch, and then the "request for merging xyz-team branch" message > to put the branch in the merge queue. That'd be neat. Some other flow/UI idea: >From the QA interface, have a "Request to build" button action attached to a branch. If the branch could be built successfully (with all checks OK), enable a "Request to merge" button, that could send an email with the patches to review to guix-patches. -- Thanks, Maxim
