Community

Creating a project release

Last updated February 28, 2013.

Once you're ready to provide a downloadable .tar.gz/.zip file of your project code, follow these steps to create a release. You can create either an official release or a development release. Read more about the types of releases.

Enabling releases

If you have not yet enabled releases on your project, do so now.

  1. Click the Edit tab > Releases sub-tab on your project page.
  2. Confirm that in the Advanced options, the Enable releases check box is checked. If this box is not checked, you will not see a link to Add new release on your project page.

Creating an official release

  1. Click the Version control tab on your project page, and follow the instructions labeled Tag for a stable release.
  2. Return to the main project page, and then click the Add new release link at the bottom of the page.
  3. Select your tag, such as 7.x-1.0, and save the form.
  4. Select the terms that correspond to the nature of the release (Features, Bug fixes), and fill out release notes.
  5. Click Save. An unpublished release node appears. Drupal.org publishes this node within 5 minutes and attaches automatically-generated .tar.gz and .zip files of your project code.

Creating a development release

  1. Click the Version control tab on your project page, and follow the instructions labeled Branch for a dev release.
  2. Return to the main project page, and click the Add new release link at the bottom of the page.
  3. Select your branch, such as 7.x-1.x, and save the form.
  4. Select the terms that correspond to the nature of the release (Features, Bug fixes) and fill out release notes.
  5. Click Save. An unpublished release node is created. This can be viewed by clicking View all releases. Drupal.org publishes this node within 12 hours and attaches automatically-generated .tar.gz and .zip files of your project code.
  6. Development releases are not displayed on your project page by default. If you'd like the development release to appear as an option in your project's downloads section, click the 'Administer releases' link at the bottom of the project page, and check the 'Show snapshot release' checkbox beside the appropriate branch.

Note: Download links will take approximately 10 minutes to publish after your release has been created.

Also note: Git submodules, while allowed by the repositories on drupal.org, will not be included in releases.

Login or register to post comments

Comments

fatal: remote error: Repository does not exist.

Posted by AaronELBorg on May 29, 2012 at 6:04pm

UPDATE: Fixed the issue but I'll leave everything here for others to see. The 'EDIT' below contains the fix.
----------------------------------------------------------------------------------------------------------------------------------------

I've just been given the 'git vetted user' role and am trying to release my first stable release.

However, when I do this:

git checkout  6.x-1.x
git tag 6.x-1.0
git push origin 6.x-1.0

I'm getting this:

fatal: remote error: Repository does not exist. Verify that your remote is correct.

Is this something to do with the fact that I'm pushing to a 'sandbox' and it's no longer a 'sandbox' since it's now an official project? Perhaps I need to change my config file?

Thanks for any info.
-----------------------------------------------------------------------------------------------------------------------------------

EDIT: Fixed it.

The issue was that my config did indeed need to be changed from the 'sandbox' one to my project page. (Actually, it was that combined with the fact that I needed a valid branch name (6.x-1.x) and a valid tag name (6.x-1.0) as well. Ended up having to delete a branch that I erroneously created called 6.x-1.0.....that's a no-go).

This issue: http://drupal.org/node/1292020
....saved me because Ben Scott included his config.txt. Nice work, Ben Scott. Nice work.

nobody click here