Plan for Backup and Migrate 7.x-3.7

I just wanted to comment quickly that it is amazing to me how many people are still wanting new features or improvements to the 7.x version. Perhaps the huge changes from Drupal 7 to Drupal 8 are discouraging users from upgrading, even though the new core release is a couple of years old by now.

It's because there are plenty of modules that don't have stable releases for Drupal 8 or PHP 7.2 yet, and migrating to Drupal 8 is a pain, especially for larger sites.

I'd say most people just want the issues fixed that have been in the queue for a few years.

@DamienMcKenna This is all so depressing. If I had known the problems with the Drupal 7 to Drupal 8 upgrade I would probably not have chosen to jump on the Drupal ship in the first place 9 years ago, though no doubt it has been a great avenue for me as a part-time web developer for my own business. The future looks a little bleak. Maybe once we get past the Druapl 8 hump things will improve, but I'm more inclined toward thinking things are going to be rough from here on out unless you are a business that has resources to self-pay for the extra things you need for your site beyond the core functionalities.

I really think this issue needs to be fixed before the next release, so that users migrating from 2.x to 3.x don't see a Fatal PHP error:
https://www.drupal.org/project/backup_migrate/issues/3023804

Also, I don't know how to add that issue as a child issue, but I think it should be one.

Not that it is any of my business, just a reminder: the end of life for Nodesquirrel is around the corner. Were you guys going to do a release for that?

Nodesquirrel issue: #3051821: Remove NodeSquirrel integration