Introduction to releases
At some point during while developing your module, theme, or translation, you will probably declare the project formally "done enough" and choose to contribute it to the community, so that they can download it from the Download section for their given Drupal version. This process is called creating a release of your project.
There are two steps to creating a release:
- Branching and/or tagging the module in CVS, which indicates that the project is compatible with a certain Drupal version, such as 4.7.x.
- Creating a release node at Drupal.org, which generates a "tarball" that users can see in the module download listing.
This document covers the second of these steps.
Creating a release node for your project
- Navigate to your project's page; for example, http://drupal.org/project/signup.
- Under the Releases heading, click Add new release. Note that you will only see this link if you are on the list of people with CVS Access to the project.
- Select the CVS identifier you want to use from the list of available branches and tags that aren't yet associated with a release.
- If you chose to create a release from HEAD, you'll see an intermediary page which prompts you to indicate the Drupal version that this release series is compatible with.
- Finally, fill in the remaining details of your release, such as a Description and click Submit. Note that there are certain fields on this form that are calculated automatically and cannot be changed.
- You will receive a message to inform you that your release has been submitted. The new release will initially be unpublished; only after the packaging scripts run (twice per day) will it become published, at which time users will be able to download a tarball of your module, theme, or translation.
Things to watch
- You will only be able to create releases for projects if you are on the list of people with "CVS access" to that project.
- Projects are only packaged once or twice a day, so it might take up to 24 hours for new releases to become available on the website or for updates to propagate to the downloads.
- If you found a bug that needs to be fixed in several releases of your project, make sure to commit the fix to the different branches unless you are no longer maintaining certain releases of your project.
- You may only create releases for modules, themes, theme engines, and translations. Personal sandboxes, items in the documentation directory of the contributions repository, etc. won't be packaged.