5.x is pretty old now, and 6.x has some nice features in it (hook ordering, drush make fixes, tty fixes, etc). I propose that we bump the minimum drush requirement to 6.x with rc5.

Comments

helmo’s picture

helmo CreditAttribution: helmo commented

relates to #2002804: [meta] depend on Drush 8.x-6.x?

+1 ... I'm not sure for who we would need drush 5 support anymore.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

I'm fine with recommending Drush 6, but Aegir 2 works just fine on Drush 5. So, I'm not sure why we'd want to do this. For Aegir 3, or certain contrib modules, Drush 6 should be the minimum.

Perhaps we'd reduce the support burden... In which case maybe we differentiate b/w the minimum required and the minimum supported?

cweagans’s picture

cweagans
He/Him
Location Boise, ID, USA
CreditAttribution: cweagans commented

One pretty strong reason is that contrib authors could depend on hook ordering being present. I had to use drush_hook_provision_verify_validate() in provision_platform_git to pull down a copy of the platform from Git. If I could depend on hook ordering being available, I wouldn't have to do that in the _validate hook (which just feels wrong to me).

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Status: Active » Closed (works as designed)

if your extension requires drush 6, that's fine, but aegir 2 doesn't.