Problem/Motivation
Drupal Recipes is the new standard moving forward, replacing the outdated sub-profile method.
The patch for #3266057: Allow profiles to define a base/parent profile [continue of #1356276] will never be committed to Drupal Core, and it has not been properly re-rolled for the latest Drupal 10 or Drupal 11 versions, leading to compatibility issues.
Proposed resolution
- Switch Vardoc to a standalone installation profile/recipe to align with the direction of Drupal Recipes and modern best practices.
- Convert internal Vardoc's default configs to recipes
Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ✅ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ✅ Code review from 1 Vardot core team member
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Update Release Notes and Update Helper on new feature change/addition
- ❌ Release vardoc-4.0.10
Varbase update type
- ✅ No Update
- ➖ Optional Update
- ➖ Forced Update
- ➖ Forced Update if Unchanged
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- Issue #3516142: Converted Vardoc to a standalone installation profile to move with the direction of Drupal Recipes
Comments
Comment #27
rajab natshahComment #28
rajab natshah✅ Released vardoc-4.0.10
Comment #29
rajab natshahNeeds work on the
5.0.xbranch