The version numbers in this queue are out of date, stopping at alpha3. This because we migrated source code away from CVS during that release. Now we're back, but we still can't make a release of this project because neither of those issues seems to be solved on Drupal.org:

#751242: Install profiles cannot create releases with a non drupal-org makefile
#1105820: converted install profile doesn't pass validation

Ideally, the first issue would be fixed and we wouldn't have to ship a drupal-org makefile that wouldn't be used anyways and would just add confusion. But as a workaround, if the second one is fixed, we could at least make a release here to update version numbers.

In the meantime, document which version of aegir is affected manually when opening the bug report.

Comments

anarcat’s picture

anarcat commented

Apparently, the former issue should be addressable shortly, somewhere next week. In the meantime, I think we can make the 1.0 release and have the makefile point to git and create the hostmaster release node once the bug is fixed so we have version numbers right at least. Then 1.1 can fix the makefile..

Anonymous’s picture

Anonymous (not verified) commented
Category: bug » task

This strikes me as more of a task to tick off for a future release once this (other, d.o) bug is fixed. Changing category

anarcat’s picture

anarcat commented

It seems drupal.org is focusing on #951978: "Unable to determine project type for drupal" when creating release right now, which is a good thing because it's going to actually fix the darn thing instead of just working around.

It seems that it's just an interoperability issue between drush_make and d.o...

steven jones’s picture

steven jones commented
Status: Active » Needs work

Hurrah! That linked issue got fixed, so we can now make some lovely release nodes.

anarcat’s picture

anarcat commented

So unfortunately, this is still not feasible, I get this trying to release 1.0 or 1.1:

The drupal-org.make file for project Hostmaster (Aegir) failed verification for Git tag 6.x-1.1.

http://drupal.org/node/642116 -- to learn more about correcting these errors.

Once these errors are fixed, commit the changes to your drupal-org.make, move the release tag for your project (check the Git manual to learn how to move tags if necessary), and submit the release node again.

Looks like #751242: Install profiles cannot create releases with a non drupal-org makefile may not be fixed after all...?

In the meantime, I have removed the drupal-org.make file to try to make this pass validation next time...

anarcat’s picture

anarcat commented
Status: Needs work » Fixed

I removed the drupal-org makefile and all is now dandy.

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