Add Drupal CMS as option in new forum posts, reduce version options

The taxonomy terms are added as feature, via code.

The same taxonomy vocabulary is also used on case studies, so we’ll want to consider the impact there as well.

We can order the options in any way, so Drupal CMS could be at the top.

Merging older versions would require a bulk update of old forum posts & case studies to the updated term. This would effectively lose the original data. Not necessarily a bad thing, just noting that this would take some work.

Thinking about this another way - is the Drupal version field still useful on forum posts? Removing the field is an option. This would also effectively be data loss.

Thinking about this another way - is the Drupal version field still useful on forum posts? Removing the field is an option. This would also effectively be data loss.

Thanks for the feedback @drumm, and simply removing the version field may be the solution. I can't think of a single time I have used the version number in the Forum. The only time I have seen any use for it, was to spot spammers, since the bot would often select the first option (at the time "Drupal 4.5.x or older") and thereby reveal themselves :)

I even thought about suggesting combining categories like this in the Issue Summary, since Drupal 8-11 are virtually identical:

• Drupal CMS
• Drupal 8-11
• Drupal 7 or older

But Drupal CMS can be any version (11, 12, etc.), so in that sense, still not very useful ...

So +1 from me, for removing Version field in the Drupal Forum. Case studies can keep a Version field of course, it may be more useful there?

In a forum post, it could be helpful to filter the posts by Drupal version, but I am not sure there are many people who do that.

I did a quick query to see what the last 1,000 published forum posts use:

   1 Drupal 10.x,Drupal 9.x,Drupal 7.x
   1 Drupal 4.5.x or older
   1 Drupal 4.6.x
   1 Drupal 6.x
   1 Drupal 7.x,Drupal 8.x,Drupal 10.x
   2 Drupal 10.x,Drupal 9.x,Drupal 8.x
   2 Drupal 7.x,Drupal 9.x
   3 Drupal 10.x,Drupal 7.x
   3 Drupal 11.x,Drupal 10.x,Drupal 9.x
   3 Drupal 11.x,Drupal 10.x,Drupal 9.x,Drupal 8.x
   3 Drupal 8.x,Drupal 9.x,Drupal 10.x
   3 Drupal 9.x,Drupal 10.x
   4 Drupal 10.x,Drupal 9.x
  11 Drupal 11.x,Drupal 10.x
  18 Drupal 8.x
  45 Drupal 7.x
  74 Drupal 9.x
  84 NULL
 133 Drupal 11.x
 607 Drupal 10.x

All but 84 (8.4%) actually do select Drupal versions. So it is used more than I expected.

With Drupal’s semantic versioning, the Drupal version is indeed a lot less significant today.

Thanks for sharing @avpaderno, but what is the way to do what you describe? ("In a forum post, it could be helpful to filter the posts by Drupal version [...]")

If you mean simply clicking the 10.x or 11.x tag under a post, you get Case studies on page #2 ... (I never clicked on those tags before earlier today)

• Drupal 10: https://www.drupal.org/taxonomy/term/195821 →
• Drupal 11: https://www.drupal.org/taxonomy/term/202774 →

Interesting stats, thanks for digging them up @drumm. With your mention of the minor differences between versions now, I interpret you as leaning towards agreeing that version can be removed, but I could be mistaken. Where do you stand @avpaderno?

We don't have to delete the field right away, it could for a start simply be hidden in the form with CSS, and we can decide later on, if we want to remove it ...

Drupal version, dev environment, and other useful info could be collected by introducing a forum post template, as I suggested in ✨ Add System and versions content template Active .

I thought the list of forum posts would show that tag, but it is not so.

If I wanted to avoid reading posts for Drupal 7, for example, I should see each forum post. At that point, I could also read the post to understand whether it is a post for Drupal 7.

Ok, great to get clarified that it's not possible. Did you all see that Case Studies are shown in the list, if you click the tag, like 11.x?

Anyway, the question is now where you both stand on removing version?