Identify the next stable release for Backup & Migrate on Drupal 9.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

DamienMcKenna created an issue. See original summary.

damienmckenna’s picture

damienmckenna’s picture

Title: Plan for Backup and Migrate 5.0.2 » Plan for Backup and Migrate 5.1.0

Let's do a feature update next.

damienmckenna’s picture

Issue summary: View changes

ppseftogiannis made their first commit to this issue’s fork.

anybody’s picture

@ppseftogiannis what's that?

Very much looking forward to the next stable release as it contains several small but helpful features for daily work! :)
Is something scheduled @Damien?

damienmckenna’s picture

Version: 5.0.x-dev » 5.1.x-dev
anybody’s picture

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

Features like #3223057: Add Drush command for running a quick backup were merged >1Y ago and would be suuuuuper helpful for us. Currently #3228379: Download errors, backup files contain trailing HTML, corrupts archive backups 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!

anybody’s picture

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

solideogloria’s picture

I think the linked issue should remain a blocker. Applying the patch from that issue also fixes the corrupted gzip file downloads issue, so it's an important fix.

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

solideogloria’s picture

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.

The other option is to merge the GitLab CI addition, and then look at the blocking issue.

grevil’s picture

Hopefully someone can find the time to fix the tests in #3228379: Download errors, backup files contain trailing HTML, corrupts archive backups. As 5.1.x is the only version currently supporting Drupal 11.

grevil’s picture

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

solideogloria’s picture

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

anybody’s picture

I agree that issue needs to be resolved or we should revert that feature for now to not block the new release!

fgm’s picture

Maybe merge #3475381: Config Schema is missing the Notify schema before someone else bumps into this too.

anybody’s picture

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

damienmckenna’s picture

Status: Active » Fixed
anybody’s picture

Yay!!! Drupal 11 release and all these great new features! Thank you soooooooo much @DamienMcKenna!!

grevil’s picture

Thanks a LOT Damien! 😍

Great stuff! 🎉🎉

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.