bug#70456: Request for merging core-updates branch

[Guillaume Le Vaillant]

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Hi,
>
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Lars-Dominik Braun <lars@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.

I'll try to merge the lisp-team branch tomorrow (UTC+2 timezone).

signature.asc
Description: PGP signature