Hello,
Josselin Poiret skribis:
> Maybe it would be a good time to create an infrastructure/CI team, and
> set some clear goals for it? I think it might motivate people (me
> included) to get more involved in GBC development if there is something
> to build towards.
Good idea!
> Also, I kind
Josselin Poiret writes:
> Hi Chris and Andreas,
>
> Christopher Baines writes:
>
>> I too would like to see improved tooling for managing changes. I've been
>> working on the qa-frontpage for smaller changes, but I think this can be
>> extended to large changes too.
>>
>> [...]
>>
>> This is so
On Wed, May 10, 2023 at 01:39:05PM +0200, Andreas Enge wrote:
> Hello all,
>
> the title says it all, I wish to share some conclusions from working on
> the core-updates merge. Clearly our tooling could be improved for the task;
> there was some flying by night without instruments, and in the end
Hi Chris and Andreas,
Christopher Baines writes:
> I too would like to see improved tooling for managing changes. I've been
> working on the qa-frontpage for smaller changes, but I think this can be
> extended to large changes too.
>
> [...]
>
> This is something I'd like to see too. I've been t
Andreas Enge writes:
> the title says it all, I wish to share some conclusions from working on
> the core-updates merge. Clearly our tooling could be improved for the task;
> there was some flying by night without instruments, and in the end I
> merged the branch without being really able to tel
Hello all,
the title says it all, I wish to share some conclusions from working on
the core-updates merge. Clearly our tooling could be improved for the task;
there was some flying by night without instruments, and in the end I
merged the branch without being really able to tell how it compared
to
