This project is not covered by Drupal’s security advisory policy.
This project provides upgrade paths for schema changes in Drupal 8 until the beta-to-beta upgrade path is officially supported in core. (And formerly did so for HEAD-to-HEAD upgrades during Drupal 7's development.)
See the README.txt for more info.
How can I contribute to this project?
Anyone can contribute a patch; if you'd like commit access, create an issue in the queue and/or ping one of the existing maintainers.
Why does this project not have a -dev tarball or stable release?
Running from an Alpha vs HEAD is like the difference between playing Jenga on a sleeping elephant to playing Jenga on a cocaine addled elephant riding a skateboard being jabbed in the ass with a hot poker. In other words, it's a wild ride. - Jacob Singh
Pre-release candidate core versions are not supported for production environments yet, so if you are using this module, it's because you're developing locally or living dangerously.
If you're living that dangerously, then you should be able to clone the module out from git.
If you're reading this and thinking "I like living dangerously, but I don't know how to clone a module from git" then this project is not for you. This project is only for experienced developers.
- Maintenance status: Minimally maintained
- Development status: Maintenance fixes only
- Module categories: Developer
- Reported installs: 20 sites currently report using this module. View usage statistics.
- Downloads: 421
- Automated tests: Enabled
- Last modified: March 25, 2015
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.