|
| 1 | +--- |
| 2 | +slug: automated-reports-changelogs |
| 3 | +title: Automated reports and changelogs |
| 4 | +authors: [castrojo] |
| 5 | +tags: [announcements] |
| 6 | +--- |
| 7 | + |
| 8 | + |
| 9 | + |
| 10 | +Hi everyone, |
| 11 | + |
| 12 | +It can be difficult to keep track of things if you're not paying attention. I've been working on ways to collate all of the things happening from across the community into a regular monthly report. Here's Jurassic January: https://docs.projectbluefin.io/reports/2026/01 |
| 13 | + |
| 14 | +Changelogs are actually pretty weird in bootc land. We usually extract the package version info from the last rechunking step to generate the changelogs - however that doesn't really cover the entire project, just the things in that repository. There's also a new upstream rechunker coming down the pipeline so that means that we'll need to rework how we generate the changelogs (thanks to [@renner0e](https://github.com/renner0e) for investigating this!). The existing changelogs also really only tell you about the things in the image, and not the "whole" of Bluefin. These will always continue to be published on [changelogs.projectbluefin.io](https://changelogs.projectbluefin.io) |
| 15 | + |
| 16 | +These reports aren't a replacement for the changelogs, just as this blog will continue to handle most of the "Why?" we do things -- for us it's a good way to blog about the meta and not the minutiae. |
| 17 | + |
| 18 | +We've divided Bluefin into the categories that match the labels throughout the project, so that we can organize things a little bit better. Each section looks like this: |
| 19 | + |
| 20 | +--- |
| 21 | + |
| 22 | +## Ecosystem |
| 23 | + |
| 24 | +   |
| 25 | + |
| 26 | +_Homebrew packages, AI/ML tools (Bluespeed), and Flatpak applications_ |
| 27 | + |
| 28 | +--- |
| 29 | + |
| 30 | +Additionally each section is divided into two categories. "Planned Work" are things we're purposely working on. These usually need planning and organization and are tracked in [todo.projectbluefin.io](https://todo.projectbluefin.io). |
| 31 | + |
| 32 | +"Opportunistic Work" are things that people just work on day-to-day and may or may not have a plan attached to them. This is usually the bulk of the work. We also needed a way to track what's going into the production homebrew tap, and in general tell people when something is getting promoted. Here's the first attempt: |
| 33 | + |
| 34 | +--- |
| 35 | +### Homebrew Package Updates |
| 36 | + |
| 37 | +  |
| 38 | + |
| 39 | +**75 automated updates** this month via GitHub Actions. Homebrew tap version bumps ensure Bluefin users always have access to the latest stable releases. |
| 40 | + |
| 41 | +#### Quick Summary |
| 42 | + |
| 43 | +| Tap | Updates | |
| 44 | +|-----|---------| |
| 45 | +| production-tap | 31 | |
| 46 | +| experimental-tap | 44 | |
| 47 | + |
| 48 | +--- |
| 49 | + |
| 50 | +We also took the opportunity to add stats on the builders so you can check out Bluefin's health "at a glance". And lastly we wanted to highlight the contributors. New contributors ("New Lights"), will have a gold foil usercard to celebrate their first Bluefin contribution: |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +Each month will list every person that contributed to Bluefin for that month, so if you're keen, apply within! This section is incomplete, it does not include discussions and issues, so if you're working in those areas you're not getting a shout out yet, but we'll keep making improvements. |
| 55 | + |
| 56 | +If there's an area of Bluefin that you're finding hard to keep track of leave feedback in this thread! |
| 57 | + |
| 58 | +## [Discussion](https://github.com/ublue-os/bluefin/discussions) |
0 commit comments