# Monthly DevOps Logs

**URL:** https://discourse.haskell.org/t/monthly-devops-logs/10103
**Category:** Haskell Foundation
**Created:** [August 6, 2024, 9:13am UTC](https://discourse.haskell.org/t/monthly-devops-logs/10103 "2024-08-06T09:13:13Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![chreekat](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/chreekat/32/2669_2.png) [@chreekat](https://discourse.haskell.org/u/chreekat)
#### Post date: [November 4, 2024, 7:38am UTC](https://discourse.haskell.org/t/monthly-devops-logs/10103/10 "2024-11-04T07:38:39Z")

</div>

> [@janus](#):
>
> But as far as I understand, the only issue with FreeBSD is the issue fixed in [MR 13276](https://gitlab.haskell.org/ghc/ghc/-/merge_requests/13276)

No, there’s another, bigger issue.

To maintain release quality, release artifacts are only generated through CI. No manual process is used.\[1\]

As long as there are no FreeBSD CI resources, there will be no FreeBSD releases.

The platform policy says, “[For Tier 2] we rely on community support for developing, testing, and building distributions.” In the past, third parties would build distribution packages. That doesn’t happen anymore. I can only assume it was a high-friction process. It makes more sense to require CI, even though that makes the platform policy a bit out of date.

* * *

1. Although a worrying amount of the rest of the release process is still manual.

---

_[View the full topic](https://discourse.haskell.org/t/monthly-devops-logs/10103)._
