Associating old "HEAD" releases with a real version
Note: This page applies only to full Drupal.org administrators with the administer projects permission.
When the current release management system was introduced, many projects had development snapshots that became "HEAD" releases. These releases do not contain any information about core compatibility and are slowly being renamed and associated with actual versions.
Additional information about these "HEAD" releases can be found in the CVS section of the handbook.
In order to rename one of the old "HEAD" releases, make the following changes:
| Field name | Old value | New value |
|---|---|---|
| Title | example HEAD | example 7.x-1.x-dev |
| Version string | HEAD | 7.x-1.x-dev |
| Drupal Core compatibility | (unset) | 7.x |
| Major | (unset) | 1 |
| Filepath | files/projects/example-HEAD.tar.gz | (delete contents) |
Then, at the next packaging run, example-7.x-1.x-dev.tar.gz will be created.
The above assumes that the project name is "Example" and the code currently in HEAD is the first version of code that will work for Drupal 7 core (7.x-1.x).
Note: please do NOT set the "Major" version to "7" and the "Patch level" to "1". I know that's tempting, but that's not how the version numbers are stored internally. If you do it this way, the update.module in core will be confused. See #317074: old dev release marked as "Up to date" for an example of when things went wrong.