Give the gift of Drupal. All merchandise is 50% off through 2016.
When creating a release for a Debut feature, there's an extra step needed because of the way the .make.inc files work.
In Debut, the .make.inc files include not only the dependencies of a Debut feature module but the feature module itself. This means that, before creating a release, it's necessary to edit the feature's .make.inc file to have the version that will be released.
If this sounds kind of circular, well, it is.... Hence this documentation page.
Say you're preparing a new release of Debut Event. The current stable release is 7.x-1.0-rc1 and the release you're about to post will be 7.x-1.0-rc2. Steps are:
- Edit debut_event.make.inc. Find the line that identifies the current version of debut_event:
projects[debut_event][version] = 7.x-1.0-rc1
Edit this to read:
projects[debut_event][version] = 7.x-1.0-rc2
- Commit the change.
- Then follow the regular steps for creating a project release.
Dependencies and releasing sets of Debut features
If your Debut feature's .make.inc includes other Debut features, which also need new releases, you'll want to update the .make.inc files all at once and then post new releases.
For example, say you've made changes to Debut Event, Debut Media, and Debut and now need to post new releases of them all. The debut_event.make.inc file includes both debut_media and debut, so the steps should be:
- Determine the next release versions for all three features.
- Edit all three features' .make.inc files to include the next release versions.
- Issue the releases.