LocalGov Drupal Docs
Overview
  • Developers
  • Content designers
  • Designers
  • Contributing
  • Accessibility
  • Governance
Microsites
Main site
GitHub
Overview
  • Developers
  • Content designers
  • Designers
  • Contributing
  • Accessibility
  • Governance
Microsites
Main site
GitHub
  • For Developers
  • Getting started
    • Drupal requirements
    • Working with Lando
    • Working with DDEV
    • Debugging with Xdebug
    • Working with Gitpod
  • General configuration
    • Content types
    • Custom modules
    • Image styles
    • Media types
    • Paragraph types
    • Taxonomies
    • User roles
  • Features
    • Services: Technical
    • Alert banners: Technical
    • News: Technical
    • Directories: Technical
    • Location Geo: Technical
    • Subsites: Technical
    • Workflows: Technical
  • Theme
    • LocalGov Base
    • Regions
    • LocalGov Theme (Deprecated)
    • Skeleton theme (Deprecated)
    • Admin theme (Deprecated)
  • Testing
  • Development workflows
    • Installing and deploying a LocalGov Drupal site
  • Hosting
    • Hosting a LocalGov Drupal site
    • Hosting LocalGov Drupal on Azure
  • Release statuses
    • Release statuses
      • Alpha releases
      • Beta releases
      • Release candidates
      • Stable release
      • Further reading
  • Security
    • Best practice guidance
    • Single Sign-On
  • Quality standards
    • Quality standards: Accessibility
    • Quality standard: Documentation
    • Quality standard: Testing
  • How-tos
    • How to use Gitpod to test modules in the browser

Release statuses

LocalGov Drupal projects aim to follow a fairly standard approach to releases.

This includes the Localgov Drupal distribution and optional contributed modules.

Alpha releases

An alpha release signifies that we are getting closer to a stable releaes, but is potentially unstable and needs more testing to flush out bugs.

For example, 3.0.0-alpha1

Beta releases

The beta relase is considered more stable, with

  • critical data loss and security bugs are resolved
  • functionality, APIs and dependencies are stable enough for others to rely on
  • most problems with upgrade paths are fixed

For example, 4.0.0-beta1

Release candidates

At times, we might make a release candidate for further testing before a stable releases.

For example, 4.0.0-rc1

(Note, we've not actually made any release candidates.)

Stable release

A stable release is considered stable, secure, performant and is aligned with our quality standards.

For example, 3.0.4

Further reading

For more information, please see drupal.org's approach to release statuses

Help us improve this page!
Last Updated: 5/20/2024, 8:25:13 PM
Prev
Hosting
Next
Security