Publishing a Minor/Major Release
This document outlines the steps the Publishing Manager needs to take to publish a new minor or major release of the AI module. When publishing a minor or major release for the AI module, follow these steps to ensure a smooth and efficient process.
Create the Tag
- Tag the minor/major release and push it up to the remote repository
- Visit https://git.drupalcode.org/project/ai/-/tags and verify that the tag corresponds to the correct version number and includes all intended changes.
- Check the diff between the last release and the new tag to ensure it matches the intended changes.
- No code confirmation should be needed for minor/major releases, since these should have been fully tested by QA.
Publish a Release
- The time for the release should have been agreed upon with the marketing team in advance to ensure proper communication.
- Go to the AI module project page on Drupal.org: https://www.drupal.org/project/ai
- Click on the "Add new release" link on the bottom of the page.
- Select the newly created tag from the "Version" dropdown menu and click next.
- Copy the CHANGELOG.md release notes into the "Release notes" field.
- We usually do not fill out the "Short description" field for minor/major releases.
- Check the "Bug fixes" or "New features" boxes as appropriate.
- Click Preview to verify the HTML formatting looks good.
- Click Save to publish the release.
Communicate the Release
- Once the release is published, communicate the release to Paul Johnson and the marketing team on Slack under #ai-initiative-marketing.