Token is particularly special in that only the API bits are in core. You need the Token module to actually have a UI for selecting them. However, it gets counted as green even though it's only in beta.

We should probably either add some special handling for this case. I originally special-cased all "in core with caveats" records, but not all are created equal. (For example, Image API has a caveat just around the imagemagick filter and one particular action, which is hardly the same thing).

Comments

effulgentsia’s picture

effulgentsia commented

Looking at the list, I think Token is the only one that shouldn't be treated as in-core, but as a still needed contrib project. I think the others are fine to consider in-core, even Image API (despite missing imagemagick) and CCK (despite missing reference fields).

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Yeah, CCK handles the upgrade path of CCK => Fields, though. And right now it's just a dev release, which looks scary as hell.