You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ensures that products can be grouped correctly even if the names are differing/incorrect. For example identified in an enterprise software catalog. Need to determine if this is part of the OPAT data (if it's a publicly accessible catalog) or perhaps as part of the directory input file, or both.
The text was updated successfully, but these errors were encountered:
I think the plan is for a new OpenACR to be released for each "Major version" as determined by the project.
I can't see issuing a separate OpenACR for Drupal 9.2 vs Drupal 9.3 but would definitely want to see one for Drupal 10.
To track this our assumption is that the file name would actually change.
In Drupal we'd likely have the OpenACR in core and within a major release would probably just rename it when we find updates to the OpenACR file: git mv OpenACR-Drupal-9.yaml OpenACR-Drupal-9-1.yaml
Likewise later when we start with the Drupal 10 version we would rename this as this would be the first OpenACR for Drupal 10: git mv OpenACR-Drupal-9-1.yaml OpenACR-Drupal-10.yaml
This would help respect those who are managing Drupal Core as well also those who just want the OpenACR file and aren't cloning the Drupal repo.
This ensures that products can be grouped correctly even if the names are differing/incorrect. For example identified in an enterprise software catalog. Need to determine if this is part of the OPAT data (if it's a publicly accessible catalog) or perhaps as part of the directory input file, or both.
The text was updated successfully, but these errors were encountered: