Voting starts in March for the Drupal Association Board election.
Back up and restore your Drupal MySQL database, code, and files or migrate a site between environments. However, beware that the 8.x-4.0-alpha1 version as of December 2016 still has an open critical issue that makes the module essentially non-functional. See Comment #31 for details. Another simpler backup module has a stable release for D8, Backup Database, but it depends upon the Composer module which may be problematic for some developers.
# Project URL
# Where is the code?
A partially functional rewrite is available in the 8.x-4.x-dev branch.
# Estimated completion date
Jeff Burnz noted in Comment #39 on December 23, 2016, in response to discussion of work picking back up on this module, "Can't see that, this module is dead. No updates for 7 or 8 months, D8 now 1 year old. Intentions are all good, but the lack of progress or communication is quite profound given the sheer popularity of this module." One of the problems discussed in Comments #36 through #39 is that as szeidler said, "Also backup_migrate will at some point depend on Composer. It's already using a library approach (hosted on github), but is currently built-in in the official alpha release and repository. But I'm pretty sure it will switch to a Composer-based workflow . . . ." Comment #39 points out usage problems among both experienced and inexperienced users of Composer but argues for proceeding with completion of this module for D8 even if Composer is required because this module's functionality is so essential. A question to be discussed is whether the module can proceed without a Composer dependency in order to avoid limiting the ease of use and popularity of this module.
None currently but may require Composer going forward; see previous point.
# Who's doing the port?
Work is being done to rewrite the module from the ground up by ronan. A co-maintainer has been requested. Volunteers are welcome, but 'feature missing' tickets are a bit premature.
# What help do they need?
Developers who are familiar with PHP OOP best practices and test writing using PHPUnit would be helpful to continue the rewrite. On December 17, 2016, Damien McKenna requested a co-maintainer to help with the current critical issue with this module.
# D8 roadmap
# Background and reference information
As of December 16, 2016, according to Comment #31, the green 8.x-4.0-alpha1 version (also dev) still has an open critical issue that leads to an irreversibly corrupted database after backup and restoring. The current export process doesn't take UTF8 into consideration, which leads to a conversion of all non-ascii characters into ?. If a user is trusting the alpha version and restoring from a backup created by this version, he will probably corrupt his database.