# Bullhorn release process
###### tags: `bullhorn`

## Upcoming Release editors
- [ ] May 24, 2024 -
- [ ] May 31 -
- [ ] June 7 -
- [ ] June 14 -
- [ ] June 21 - Leo
- [ ] June 28 - Leo

**NOTE** The biweekly release editor is responsible for going into the social matrix channel and checking that newsbot items have the correct emojis. If a newsbot entry doesn't have a confirmation message, add :o: so newsbot picks the message up.
**NOTE** Also chedk for the correct category flags for each entry. See [Ansible Bot Config](https://github.com/ansible-community/ansible.im/tree/main/bots) for sections/projects.

## Newsbot

* Go to the "Newsbot Admin" matrix room (ping cybette/gwmngilfen for access).
* Optionally, type`!status` to see list of news items submitted for current issue. (A bug sometimes prevents this step from working. If it doesn't produce a list of bot entries quickly, go on to the `!render` step below and manually add any additional content to the rendered .md file).
* [Check for additional content](#Check-for-additional-content) and newsbot them if needed.
* `!render` to generate the markdown file for the issue
* Create a [new forum topic](https://forum.ansible.com/c/news/bullhorn/17) in the Newsletter/blog area
* title: The Bullhorn #xxx
* tags: Add tags based on the content (releases, community, awx, for example)
* Load the content of `rendered.md` into the forum draft
* Check if there are unassigned items, refer to [Ansible Bot Config](https://github.com/ansible-community/ansible.im/tree/main/bots) for sections/projects

## Check for additional content

* Add/update Key dates section. Note DaWGs meeting happens on the next Tuesday, community WG on the Wed, and Bullhorn deadline on the Thursday. Check roadmaps above for upcoming releases.

## KEY DATES ⏱️

> * 2024-05-14: [DaWGs meeting](https://forum.ansible.com/t/documentation-working-group-agenda/153), 15:00 UTC
> * 2024-05-15: [Community WG meeting](https://forum.ansible.com/tags/c/workflow/meetbot/16/community-wg), 18:00 UTC
> * 2024-05-16: [Bullhorn #137 content deadline](https://forum.ansible.com/t/about-the-newsletter-category/166), 18:00 UTC
> * 2024-05-20: ETA for Ansible-Core 2.16.7
> * 2024-05-21: ETA for Ansible 9.6.0 release

## MAJOR NEW RELEASES 🏆️

* [ansible-devel mailing list](https://groups.google.com/g/ansible-devel) for release announcements (I use this instead of ansible-announce because ansible-core shares pre-release announcements only to ansible-devel). Note newsbot already pulls in releases announced to ansible-announce.
* [Community working group meeting notes](https://forum.ansible.com/tags/c/workflow/meetbot/16/community-wg) for any discussions asking for feedback/votes
* [Meetup report](https://connect.eng.ansible.com/meetup/meetup_report.html) for any upcoming meetups
* [ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) and [ansible-core roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_core_roadmap_index.html) for key dates around releases (e.g. feature freeze)

## Edit the markdown file

* remove the Frontmatter
* Edit the Bullhorn number within the forum draft to match the current number (see the [newsletter category](https://forum.ansible.com/c/news/bullhorn/17) for the last number):
* *Issue #137, 2024-05-10

## Mailchimp

* Log in
* Edit the header graphics
* check spacing
* ..
* Update hackmd with published time and link

## Sharing to other channels

* create bitly link via https://bit.ly/ from the forum topic
* shorten to https://bit.ly/thebullhorn000
* replace 000 with issue number

* announce in #social:ansible.com
* @room :postal_horn: The Bullhorn issue 000 is now available! {provide a couple of highlights} <forum post link>
* Post to mastodon if you have access (or ping the community team) - unpin last bullorn and pin this one after posting.
* post to Ansible subreddit `r/ansible`.
* Initial post will be blocked by reddit so go into the mod queue to approve it.
* Will have to go into prior bullhorn post, clicke the mod shield, and unpin the old before you can pin the new.

## Clean up

* `!clear` in the Newsbot Admin matrix room to clear the list for next issue submissions