As part of #1371302: Remove restriction on -dev releases in distributions we're going to be much more permissive about what you can use to define versions of stuff in your .make files. So, we're going to want to document:

A) What's now allowed.

B) Why it's a bad idea to use the magic features to find-the-latest-recommended-release. Even though we allow this, it's a bummer since if you checkout a distro from a given release tag and run drush make on the drupal-org.make file, you'll potentially end up with totally different code each time you do it. It's vastly better to have reproducible builds, and that means being explicit in the .make file about what versions of everything you want.

Comments

dww’s picture

Assigned: Unassigned » dww
Status: Active » Needs review

webchick suggested I put this as a Best practices section at Full example drupal-org.make file as that's a more likely place people will read it than as a separate sub page of Packaging a distribution on Drupal.org.

dww’s picture

Status: Needs review » Fixed

webchick had a chance to review this in IRC:

[10:23am] webchick: dww: that looks good. not sure it's in the right place, on reflection, but we could always copy/paste it somewhere else later if we want. :)
[10:25am] dww: webchick: so, should I just mark https://drupal.org/node/1403356 fixed, do you want the honors, or should we spend more energy on finding a better home for this wisdom?
[10:29am] webchick: dww: go ahead and mark it fixed

Yay,
-Derek

Automatically closed -- issue fixed for 2 weeks with no activity.