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

[Junio C Hamano <gitster@pobox.com>]

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.

* linux-feature-testbed

  Positions the job as a testbed specifically for experimental
  features, which aligns perfectly with its testing nature.

* linux-exotic-features

  Keeps the "exotic" keyword you proposed but qualifies it with
  "features", immediately removing the risk of sounding like an
  exotic Linux distribution.

== Build & Configuration Focus ==

* linux-nondefault / linux-nonstandard

  A build that departs from the standard, out-of-the-box
  configuration.

* linux-extra-knobs

  Uses Git-centric terminology.  Since you customize build-time
  configuration knobs to enable these experimental features, this is
  highly descriptive and intuitive for developers.

* linux-super-tweaked / linux-highly-tweaked

  Emphasizes that the build variables have been heavily customized.

* linux-custom-vars

  A direct, no-nonsense replacement for 'linux-TEST-vars' that
  clarifies that the variables are custom/customized rather than
  just "test" variables.

== Testing & Robustness Focus ==

* linux-stress-features

  Implies that we are stretching the capabilities of the build by
  turning on non-standard configurations.

* linux-edge-cases

  Focuses on the goal of the job: testing edge cases enabled by
  experimental configuration variables.

* linux-all-features

  If the experimental variables essentially turn on all optional
  features, this is a very clean and positive name.
k