Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 37 ยท Getting Started

Drupal Community, Distributions and Release Cycle

Understand the Drupal community, drupal.org, contributed modules, distributions, Drupal CMS, semantic versions and how major, minor and security releases work.

Drupal is more than a download. It is a community of developers, site builders, designers and companies that share code through drupal.org, the project's home. Knowing how that community releases software helps you pick the right version, trust (or question) a module, and plan upgrades without surprises.

This lesson covers the ecosystem and the release rhythm. Exact version numbers change over time, so we focus on the rules, which stay stable, and tell you where to look for the current dates.

Where things live

  • drupal.org hosts documentation, the issue queue, project pages and the security team's advisories.
  • Project pages (modules, themes, distributions) show a description, maintainers, releases, usage statistics and the issue queue. A project page is your first source of truth about a module.
  • Packagist-style delivery: you install projects with Composer from drupal/<project_name>, served by the Drupal package repository.
  • Slack and forums offer community help, and local meetups and DrupalCon bring people together.

Core, contrib and custom

Everything on your site belongs to one of three groups:

Group Meaning Where it lives
Core Shipped with Drupal, maintained by the core team web/core
Contrib Free projects from drupal.org web/modules/contrib, web/themes/contrib
Custom Code you or your team write web/modules/custom, web/themes/custom

Keeping them separate matters. You never edit core or contrib files directly, because the next update would overwrite the change. You extend behavior with your own custom module instead.

Judging a contributed module

Before adding a module, check its project page:

  • Maintenance status (actively maintained, minimally maintained, unsupported).
  • Development status (under active development, maintenance fixes only, obsolete).
  • Compatibility with your Drupal major version.
  • Last release date and the activity in the issue queue.
  • Usage count: widely used modules have more eyes on them.
  • Security coverage: projects covered by the security team show a badge; others do not receive advisories.

A module with no compatible release for your Drupal version is a risk, however attractive.

Distributions and starter kits

A distribution bundles core with modules, configuration and sometimes sample content to fit a purpose, for example a publishing platform or a community site. Drupal also offers a recommended starting point called Drupal CMS, a packaged product that comes with preconfigured features and helpers, aimed at people who want a working site fast. You can also begin with the plain standard or minimal installation profiles that come with core.

An installation profile is the mechanism behind this: it decides which modules are enabled and which configuration is imported when you run the installer.

Semantic versioning and releases

Modern Drupal uses semantic versioning: MAJOR.MINOR.PATCH.

  • A patch release (for example x.y.1 to x.y.2) contains bug fixes and security fixes. Apply them promptly.
  • A minor release (x.1 to x.2) adds features and deprecates old APIs, while staying backward compatible. Minor releases arrive roughly twice a year.
  • A major release (such as 10 to 11) removes APIs that were deprecated earlier. Because deprecations are announced in advance, upgrading between majors is largely a matter of removing deprecated calls, not rewriting the site.

Each major version has a support window, and each minor version is supported until a newer minor arrives (with some overlap and one long-term-support style minor per major). Always check drupal.org for the current schedule: do not rely on memory or this lesson for dates.

Security releases

The Drupal Security Team reviews reported vulnerabilities and publishes Security Advisories with a risk score and affected versions. Security releases are scheduled on set days, so site owners can plan. Your job is to run composer outdated "drupal/*" or the Update Status module's report, and apply updates quickly.

A version-checker you can run

This stand-in classifies an upgrade the way semantic versioning does. It is a small sketch of the rule, not a Drupal tool.

JS Stand-in: classify an upgrade

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Scoring a module

You can also turn the project-page checklist into a function. Again this is a stand-in for judgment, not a replacement for it.

JS Stand-in: module health score

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Contributing back

You do not need to be an expert to contribute. Report bugs in the issue queue with clear steps, test patches, improve documentation, or answer questions. Contributions are credited on drupal.org, and many employers value that record.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where should you put your own site-specific module code?

    Custom code lives in its own folder so updates to core and contrib never overwrite it.
  2. 2. What does a patch-level release usually contain?

    Patch releases fix bugs and vulnerabilities and are normally safe to apply promptly.
  3. 3. What is an installation profile?

    Profiles such as standard or minimal choose the initial modules and configuration.
  4. 4. Why check a module's security coverage badge?

    Only covered projects receive coordinated security advisories.

Summary

  • Drupal's community shares code on drupal.org; you install projects with Composer.
  • Separate core, contrib and custom code, and never edit core or contrib directly.
  • Judge modules by maintenance, compatibility, usage and security coverage.
  • Semantic versions: patch for fixes, minor for features, major for removing deprecated APIs.

Next: System Requirements and a Local Setup