Deprecate the repository to not mislead the a new customers of the Backdrop CMS

[dstorozhuk]

I spend 4 hours figuring out why this extensions does not work, while it is indicated as "official" bridge between Backdrop and Drush.
Some documentations referencing to it https://backdropcms.org/project/drush.
This plug installed by default in lando, ddev.

I propose:

1. Deprecate and archive this repository
2. Add links to the Bee in this project description
3. Inform lando, ddev teams that this project is not supported for 2 years or more.
4. Provide instructions to lando, ddev teams how to integrate Bee to their projects.

[dstorozhuk]

Related issue:
#254
PR that was created 3 years ago:
#251

[omega8cc]

Just a note that we maintain Drush 8 fork which supports PHP 8.2 and we even use it to maintain Drupal 10 sites in Aegir. Even more importantly we aim to add Backdrop CMS support in Aegir and even replace Aegir admin interface with Backdrop, so deeper integration with Drush 8 is being worked on.

[quicksketch]

Thanks @dstorozhuk. I think we should do most of the suggestions, including deprecating this repository and updating the README and project page to point towards bee. We always knew that Drush 8 would only last for so long, and with D7 EOL (finally) around the corner Drush 8 support isn't going last much longer either.

I can do some basic maintenance on this extension, but #251 is still pretty unclear if that's an acceptable solution. Circumventing DBTNG's escaping seems like it would only help the initial errors but still leave a bunch of other new errors that share the same problem. I'll look into it.

[quicksketch]

I merged #251 to indicate this project is deprecated in the README. @dstorozhuk if you have suggestions about further changes please file a PR if you can, or just post a comment here.

[laryn]

@omega8cc I'm curious to hear more about your plans. Care to open a topic on the forum or in Zulip? How long do you plan to support the forked version of Drush 8? Would switching the Backdrop portion of your sites to bee be feasible, so you could focus Backdrop cli development there?

[omega8cc]

@laryn We have opened a feature request although not sure if that’s the best place to discuss this topic. Suggestions and guidance are appreciated since we are new here.

Here’s the issue: backdrop/backdrop-issues#6453 (comment)

We have explained there why keeping Drush 8 support would be preferred, even if we consider Bee too.

We will support our Drush 8 fork for as long as we will support Drupal in our BOA stack because it’s our only backend. So basically forever.

[dstorozhuk]

@laryn We have opened a feature request although not sure if that’s the best place to discuss this topic. Suggestions and guidance are appreciated since we are new here.

Here’s the issue: backdrop/backdrop-issues#6453 (comment)

We have explained there why keeping Drush 8 support would be preferred, even if we consider Bee too.

We will support our Drush 8 fork for as long as we will support Drupal in our BOA stack because it’s our only backend. So basically forever.

@omega8cc could you please share the link to your fork?
I will propose the PR will readme change to point to your fork for that one who needs old drush 8 support.

[dstorozhuk]

I merged #251 to indicate this project is deprecated in the README. @dstorozhuk if you have suggestions about further changes please file a PR if you can, or just post a comment here.

I think the next step will be to mark the repo as archived https://docs.github.com/en/repositories/archiving-a-github-repository

[omega8cc]

@dstorozhuk Thank you! Here’s the repository: https://github.com/omega8cc/drush

[klonos]

@omega8cc (and others reading this thread in the future) FYI, I've opened a thread in our Zulip chat about this: https://backdrop.zulipchat.com/#narrow/stream/218635-Backdrop/topic/Aegir.2C.20drush.208.20fork.20.26.20Backdrop

[klonos]

...wondering if/how https://github.com/drush-ops/drush-launcher might help if we threw it in the mix 🤔

[omega8cc]

@klonos Thank you! Regarding drush launcher — we don’t need it at all because we don’t plan to use Drush other than version 8 which can be installed globally, outside of the site’s codebase. The launcher was for those unable to maintain shell aliases and using Drush embedded in the Drupal 8+ codebase to avoid conflicts between Drupal core and Drush dependencies after both moved to Symfony which made installing newer Drush versions as standalone deprecated and now not even possible.