Re: Feature branches

[Christopher Baines <mail@cbaines.net>]

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


Andreas Enge <andreas@enge.fr> writes:

> Am Mon, May 08, 2023 at 10:15:56AM -0700 schrieb Felix Lechner:
>> How about requiring prior to merging a feature branch that substitutes
>> exist for all changed derivations? It would prevent build failures and
>> preempt local builds, and thereby improve the experience for average
>> users.
>
> Taken absolutely, that sounds a bit excessive; but the idea is of course
> there, the branch should be built out as much as possible.
>
> It is probably unavoidable that some things stop working going forward,
> and I wonder how realistic it is to iron out all problems before a merge.

I think the thing next to aim for is at least to be informed about the
effects of any changes.

Knowning the x package breaks on y architecture and deciding to merge
anyway is a lot better (and I think the end goal) than the current
situation of not really knowing what the effects of non-trivial changes
are.

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