1.5M ratings
277k ratings

See, that’s what the app is perfect for.

Sounds perfect Wahhhh, I don’t wanna
In order to better support the fearless Drupalists building sites on Drupal 8 releases, the Drush project is adopting a new release schedule. We will release a new Drush each time that Drupal 8 releases a significantly new beta or release...

In order to better support the fearless Drupalists building sites on Drupal 8 releases, the Drush project is adopting a new release schedule. We will release a new Drush each time that Drupal 8 releases a significantly new beta or release candidate.

The list below shows a recent release of Drupal 8, and its corresponding release of Drush. It also lists the pairing for the upcoming Drupal 8 release, anticipated for March 25.

  • Drupal 8.0 beta 7 plays nicely with Drush 7.0-alpha9
  • Drupal 8.0 beta 8 will play nicely with Drush 7.0-rc1

These synchronized releases will continue until the stable release of Drupal 8.0.0. After that, the Drush project will resume an independent release schedule.

Note to the future: See the release notes for an always-current release pairing.

Improve drupal.org code workflow with git merge

Drupal.org uses a patch based workflow in order to improve its software. Today I present a concrete instance where this significantly slowed us down. Views performance work is blocked when it didn’t have to be.

Today, Dries committed a fine patch by Sun which moved a lot of test files into a happier place. After that commit, Dries reviewed Daniel’s Views patch which changed a couple of those same test files. Daniel’s patch failed to apply so Dries changed the issue to Needs Work. This doesn’t need to happen anymore. Git knows about file moves and can overcome this problem when we use it fully. If Daniel’s change was a merge instead of a patch, git uses its ancestry to apply changes to the moved test files. Try for yourself - the commands I ran are below.

We could all increase our velocity by using a merge workflow. Think of all the patches that need reroll currently which would not need reroll. Think of all the patches considered disruptive when they don’t need to be. I know that we can’t avoid all ‘Needs reroll’ events, but we can avoid a lot.

For now, I encourage folks to use d.o. sandboxes or Github to host their forks, and to post git merge commands into the issue queue instead of uploaded patches. Discussion of these changes should remain in the main issue queue. I think we should document this workflow at Drupal.org Git tutorials.

Feedback welcome.


Start from a clean 8.0.x:

# Create  branch whose tip is the commit before Sun's
$ git checkout -b daniel ebace9e
#Apply Daniel's patch
$ wget -O tmp.patch https://www.drupal.org/files/issues/1849822-view_render-19.patch; git apply tmp.patch;
$git commit -am "Fix #1849822. Convert (HTML) view rendering to a render array"
#Switch to main branch
$ git co 8.0.x
#Merge Daniel's patch and watch git's work its magic
$ git merge daniel
Auto-merging core/modules/views/tests/src/Unit/Routing/ViewPageControllerTest.php
Auto-merging core/modules/views/tests/src/Unit/Plugin/Block/ViewsBlockTest.php
Merge made by the 'recursive' strategy.
 core/modules/rest/src/Plugin/views/display/RestExport.php 
 core/modules/user/src/Tests/UserBlocksTest.php
 core/modules/views/src/Annotation/ViewsDisplay.php
 core/modules/views/src/Plugin/Block/ViewsBlock.php
 core/modules/views/src/Plugin/views/display/Attachment.php
 core/modules/views/src/Plugin/views/display/DisplayPluginBase.php
 core/modules/views/src/Plugin/views/display/Feed.php
 core/modules/views/src/Routing/ViewPageController.php
 core/modules/views/src/ViewExecutable.php
 core/modules/views/tests/src/Unit/Plugin/Block/ViewsBlockTest.php
 core/modules/views/tests/src/Unit/Routing/ViewPageControllerTest.php
 core/modules/views/views.module
 core/modules/views/views.theme.inc
 13 files changed, 147 insertions(+), 32 deletions(-)

Drush 6 Released, Moves to Github.

Drush 6 Release

The Drush team is thrilled to announce the release of Drush 6. Full release notes are there.

The highlight of Drush 6 is the new outputformat system. You can now request Drush output in easily parsed formats like json, csv, yaml etc.

Please come to our lab at Drupalcon Prague for in-depth discussion and hand-on learning about Drush 6.

Note: if you are using Drupal 8, you should stick with a frequently updated clone of master branch. Drush 6 supports Drupal 6+7 but not Drupal 8.

Drush Project Moves to Github

The Drush project has moved to Github. Update your clones!

See our wiki page which details the motivations and details surrounding this move.

Drush loves Github

drupal drush