Re: [PATCH v2 5/8] ci: rename linux-TEST-vars job

[Patrick Steinhardt <ps@pks.im>]

On Tue, Oct 13, 2026 at 07:47:35AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> >> Seeing "linux-exotic", I would think of a job running tests on an
> >> exotic Linux distro, or on an exotic platform...  but it wouldn't
> >> occur to me that it intends to set a bunch of GIT_TEST_* variables,
> >> simply because there is nothing in its name to indicate that.
> >> 
> >> I think this patch makes things worse.
> >
> > ... I think it's still a fair point. The question is whether we can come
> > up with a better name then that is not an eyesore and that gives you a
> > clue what the job is doing without you having to know about the
> > underlying mechanism.
> >
> > A couple of names that come to my mind would be "linux-nondefault",
> > "linux-optional-features"... and not much else. Do you have any
> > suggestions?
> 
> Among the following, my current favourite is "feathre testbed".
> 
> == Feature & Capability Focus ==
> 
> * linux-experimental-features / linux-experimental
> 
>   Directly states that the job enables experimental features.  This
>   is clear, standard industry terminology, and avoids any ambiguity
>   about the Linux distribution itself.

Not all of the features are experimental though, so I feel like this is
a bit misleading.

> * linux-feature-testbed
> 
>   Positions the job as a testbed specifically for experimental
>   features, which aligns perfectly with its testing nature.

I like this one, will adopt the naming. Thanks!

Patrick