Close #3586 Set lifecycle key in info files if not stable.

[trackleft]

Description

Added lifecycle: experimental attribute to the following modules:

• az_core/az_enterprise_attributes_import
• az_course
• az_curated_views
• az_demo
• az_digital_asset_library
• az_event/az_event_trellis
• az_finder
• az_http
• az_marketing_cloud
• az_migration
• az_news/az_news_export
• az_news/az_news_feeds
• az_paragraphs/az_paragraphs_link_group
• az_paragraphs/az_paragraphs_views_side_by_side
• az_publication
• az_publication/az_publication_bibtex
• az_publication/az_publication_doi
• az_publication/az_publication_import

Related issues

Close #3586

How to test

Enable an experimental module and see a warning that says to use at your own risk.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.

[bberndt-uaz]

Works as expected!

[trackleft]

Follow up lifecycle link improvement with policy link #3477