Please follow the steps outlined below when creating releases of distributed features, modules and themes.
To ready a release, do the following:
Confirm the project
Open the .info file of your project. Check to make sure the project is set to
project = projectname. Example:
project = catid.
Confirm the project status URL
In the .info file of your project. Check to make sure the project status url is set to
project status url = https://features.uni.edu/fserver.
Change the version of the project
In the project .info file, change the version of the project to a higher release. Example:
version = 6.x-1.1 to
version = 6.x-1.2.
You may use -alpha, -beta, -rc "extra versions" to signify a specific pre-release status. Example:
version = 6.x-1.0-alpha,
version = 6.x-1.0-beta2,
version = 7.x-1.0-rc2.
Fix permissions on project files
Sometimes file permissions get changed while updating files. Folders need to be set to "755" and files to "644".
One way to easily change file permissions is through the command line.
First, open your command prompt and use the
cd command to change directory to where your project is saved.
Then run the following script:
find projectdirectory -type d -print0 | xargs -0 chmod 755 ; find projectdirectory -type f -print0 | xargs -0 chmod 644
projectdirectory is the folder in which you've stored your theme, feature or module.
For the CatID module, we would use:
find catid -type d -print0 | xargs -0 chmod 755 ; find catid -type f -print0 | xargs -0 chmod 644
Compress your project directory into a .tgz file
Use tar to compress your project directory into a .tgz archive.
tar -czvf projectdirectory-drupalversion-moduleversion-extraversion.tgz projectdirectory/
For the Catid Module, we would use:
tar -czvf catid-6.x-1.0-alpha7.tgz catid/
If you're using git and want to remove git's .git folder, you'd want to use --exclude:
tar --exclude=.git -czvf catid-6.x-alpha7.tgz catid/
Create new Release node
Sign into the UNI Drupal feature server: http://www.uni.edu/features/user/login
A black administration bar will appear on the left side of the screen. If it does not, click on the wrench in the upper-left corner of the screen.
Click Create content, then Release.
Upload the .tgz package you archived earlier.
Next, select the Project that this applies to this release.
Select the version information that applies to this release. This information should match the version information you supplied during the Compress your project directory into a .tgz file step.
Select whether this is a recommended or security release. The recommended releases will be displayed on the project page. The latest recommended release per major version will be offered for update status, which is what a Drupal site checks against for updated modules, features, and themes.
Add release notes. It's important to identify any new features in a new release as well as all major changes since the last version. Also note any changes in dependant modules or if there will be any issues with upgrading.