Blog post: Removal of support for legacy storage in 13.0
The blog-post should link to existing documentation on how to migrate from legacy to hashed storage, explain why we are making the change and what to expect from 13.0 ahead in terms of deprecation/removal.
Short summary:
- In %13.0 Hashed storage will be required (system checks will fail, will not be possible to switch to legacy anymore)
- In %13.1 or %13.2 we will remove code support for legacy storage
- Suggest that before running the hashed storage, upgrade to the latest stable version (before %13.0)
- New installations since %12.0 (verify if this is the correct version) are already using hashed storage by default
- We've successfully migrated GitLab-dot-com
Edited by Gabriel Mazetto