Re: Tooling for branch workflows

[Christopher Baines <mail@cbaines.net>]

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]


Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Chris and Andreas,
>
> Christopher Baines <mail@cbaines.net> 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 thinking about this
>> already and want to spend more time working on at least making it easier
>> for more people to get involved. Let me know if you have any specific
>> requests!
>
> 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.

There's the core team, although maybe this doesn't cover this.

However, framing is important and we don't really want
infrastructure/CI, they're means rather than goals.

I'd frame any team stuff around what's wanted like substitutes and up to
date packages.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]