Release cycle

Following in the footsteps of Drupal and the release of Drupal 8.0.0, the UIkit project maintainers are committing themselves to a release cycle schedule in order to meet the growing demand and interest in UIkit for Drupal. This document describes the release cycle for all versions of UIkit (including UIkit 7 and 8) from August 26, 2016 on.

Note: 7.x-x.x/8.x-x.x versions refer to UIkit for Drupal project versions. v2.x.x/v3.x.x versions refer to UIkit framework versions.

The minor version numbers in this table assume there are no unscheduled minors. If an unscheduled minor is released, the dates will not change, but subsequent minor version numbers will be incremented accordingly. Minor versions will always match the major version of the UIkit framework the branch supports.

Past milestones

These are past milestones for each branch of UIkit for Drupal. The most recent feature release for each branch are listed for Drupal 7. The most recent releases for Drupal 8 will be beta releases until the UIkit framework is out of beta.

May 01, 2017 7.x-2.3 released
May 14, 2017 8.x-2.4 released
May 01, 2017 7.x-3.0-beta2 released
May 01, 2017 8.x-3.0-beta2 released

Current development cycle

These are the planned releases during the current development cycle. This schedule is not definitive and may be updated when the need arises.

Week of May 22, 2017 7.x-2.5-beta1 and 8.x-2.5-beta1 tagged
Week of June 5, 2017 7.x-3.0-beta3 and 8.x-3.0-beta3 tagged
Week of June 19, 2017 7.x-2.5-rc1 and 8.x-2.5-rc1 tagged
Week of July 3, 2017 7.x-3.0-beta4 and 8.x-3.0-beta4 tagged
Week of July 17, 2017 7.x-2.5 and 8.x-2.5 released

Development Cycle Key

  • Opened: The initial published release on a feature branch which begins the development phase, i.e. 7.x-2.x-dev.
  • Tagged: An unpublished tag on a feature branch which continues development, i.e. 7.x-2.1-beta1.
  • Released: A published release on a feature branch which is fully stable and recommended for use on production sites, i.e. 7.x-2.0.

Published releases will be listed under Downloads on the UIkit project page. Unpublished releases are available in the Git repository as tags but will not be listed on the UIkit project page.

New releases and opened development branches will be released bi-weekly, with 7.x-2.x/8.x-2.x branches one bi-weekly cycle and 7.x-3.x/8.x-3.x branches the other bi-weekly cycle. This will allow the maintainers to focus on a single UIkit framework version at a time. The only exception to this will be critical/security releases. This cycle may change in the future based on development needs.

Key considerations for future major releases:

  • Once UIkit framework v3.0.0 is released we will change the release cycle above so 7.x-3.0 and 8.x-3.0 are released together.
  • Subsequent releases on the 7.x-3.x and 8.x-3.x branches will be released together in the same release stages (i.e. 7.x-3.1-dev and 8.x-3.1-dev will be opened the same week).
  • The 7.x-2.x and 8.x-2.x will then enter a feature freeze and also be released together in the same release stages (i.e. 7.x-2.5-dev and 8.x-2.2-dev will be opened the same week).
  • Once the feature freeze on the 7.x-2.x and 8.x-2.x branches is in place only critical and security fixes will be considered. We will continue to support these branches but will also shift our main focus to the 7.x-3.x and 8.x-3.x branches.
  • Any modules or sub-themes released by the maintainers of UIkit will also keep in mind the above under considerations during development of those projects. This will allow all supported modules and themes to align their development with UIkit base theme project.
  • If the UIkit framework opens a v4.x.x release, the 7.x-2.x and 8.x-2.x branches will enter an End of Life cycle. Once v4.0.0 is released 7.x-2.x and 8.x-2.x will then become unsupported and their releases removed from the UIkit project page.
  • Following the above point, the maintainers will always support the two most current UIkit framework versions so themers and developers can prepare their projects for upgrades to the latest framework version. Those who do not update their projects before the End of Life will have their projects removed from the supported modules and themes section of the UIkit project page.

Key considerations for future minor releases:

  • Beginning with 7.x-3.0 and 8.x-3.0, each minor release will have a development, beta and release candidate stage. Alpha stages will no longer be used beyond this point.
  • The primary purpose of the release candidate phase is to stabilize the minor version for release. Any new features which do not make it into the next minor release will be moved the subsequent minor release.
  • There will be a minimum of 1 month between the release of a new minor release and public disclosure of any security issues that affect the previous minor, in order to ensure all sites have adequate time to upgrade. This follows Drupal's guidelines for public disclosure of security issues.
  • An open feature development phase for each minor version may begin when the branch is opened, or may begin later, depending on critical and major technical debt for the branch.

Note: It is important to keep the update module enabled to ensure you receive updates in a timely manner. Otherwise, be sure to enable the update module and check for updates at least twice a month.