This site is a static archive of the Aegir community site. Documentation has moved to http://docs.aegirproject.org. Other community resources can be found on the Contacting the community page.
Skip navigation

Dropping the master branch until the 1.0 release

Help

Dropping the master branch until the 1.0 release

When we announced the 1.0 freeze, we also announced that the master branch was opened for development. Since we're hard at work polishing the 1.0 release, we're not really doing development on the master branch for the 2.0 release.

Right now I am mostly committing to master and merging everything to the stable branch, which is just silly and a waste of time. Besides, we wouldn't be able to make releases on the master branch because of Drupal.org conventions (you can't release from master in git.drupal.org).

I will therefore simply drop the master branch until we release Aegir 1.0, at which point a 7.x-2.x branch will be created from that point. Hopefully this will not break too many things. Worst case the branch can be recreated from the 1.x branch again if necessary.

Need help?

Discussion

The discussion area lets your team communicate by posting updates and discussing issues. It is a great place for sharing progress, discussing challenges, and exploring ideas.