- Issue created by @Balu Ertl
There are signs suggest that not I am the only one who is not accustomed yet to major core versions changing in a relatively “short” period. After the D7 era spanned over a decade, D8 was with us also for many long years, and then the “next-major-version-number-everyone-talks-about” started just changing faster. With D11 around the corner being released in about two months, every mention of D10 in the context of “the-future-we-prepare-for” might confuse some.
Having our release process finally settled on a predictable delivery following a fixed timeline ( “major versions are released every two years” → ) I'd suggest opening a discussion about leaving out any numerical references of Drupal core in any written communication or documentation of the Project Analysis project.
(Also worth mentioning here Ivan Stegic's (Ten7) blog post “Just Say Drupal”, although his viewpoint is mainly based on a marketing approach targeted to a non-tech audience.)
Naturally, it does not mean “prohibiting” mentioning D10, D11, or D12, etc. when necessary (eg. discussing a specific issue), not at all. Instead, my suggestion is rather about that when we talk about the Project Analysis project in general, then use the phrase “next major version of Drupal core” and not tieing strictly to a given version number which will change by time, for sure.
Active
Miscellaneous