Plan for Backup and Migrate 5.1.0

Hi @DamienMcKenna, may I ask if there's a plan for the 5.1.0 release? At least as alpha or so?

Features like 📌 Add Drush command for running a quick backup Fixed were merged >1Y ago and would be suuuuuper helpful for us. Currently 🐛 Download errors, backup files contain trailing HTML, corrupts archive backups Needs work is the only open child issue left here. That's an issue which is already present in 5.0.x - is it a blocker?

We'll try to help now to push things forward. Would be cool to have your feedback :)

Thanks!

@DamienMcKenna I think we should not treat 🐛 Download errors, backup files contain trailing HTML, corrupts archive backups Needs work as a blocker. Anything else that prevents 5.1x from being tagged? Asking my questions from #9 again.

I think the linked issue should be a blocker. Applying the patch from that issue also fixes the corrupted gzip file downloads issue.

All that's left is to fix a failing test, I think. The code fix itself is simply adding a call to exit()

It looks like the blocking issue is stalled (I'm unsure of how to fix the test). In addition, the GitLab CI issue needs to be merged in order for tests to be run.

So maybe we should release 5.1.0 with what is ready, and hope to get the blocking issue in later.

Hopefully someone can find the time to fix 🐛 Download errors, backup files contain trailing HTML, corrupts archive backups Needs work . As 5.1.x is the only version currently supporting Drupal 11.

The gitlab ci issue IS merged, we just need to rebase that branch.

It wasn't merged at the time I commented, but I'm glad it is now.

I'd also vote to skip that issue for now. It's not as important to be a blocker IMHO.

Maybe merge 🐛 Config Schema is missing the Notify schema Needs review before someone else bumps into this too.

Thanks @fgm, good point, I'll review that one.