Skip to content

Commit 7912cf2

Browse files
authored
Merge pull request #663 from voxpupuli/release_at_speed_of_light
New blog post abpout releases.
2 parents fe2c82c + 62c94ec commit 7912cf2

1 file changed

Lines changed: 52 additions & 0 deletions

File tree

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
layout: post
3+
title: OpenVox Releases at speed of light (almost)
4+
date: 2026-04-16
5+
github_username: tuxmea
6+
---
7+
8+
The community has put lots of effort into automating the OpenVox release process.
9+
10+
To give you an example how fast releases are possible, I want to point you to the timing between the last two releases:
11+
12+
Release 8.26.0 was tagged on April 14 2026 at 6:39 PM CEST.
13+
14+
The release was available on the [GitHub release page](https://github.com/OpenVoxProject/openvox/releases/tag/8.26.0) on April 14 2026 at 6:40 PM CEST.
15+
16+
The packages were available on the repo server on April 14 2026 at 7:02 PM CEST.
17+
18+
A bug was reported on April 15 at 2:13 PM CEST via [Vox Pupuli Slack](https://voxpupuli.slack.com/archives/C088QSEH1RA/p1776255199310549).
19+
This was the message:
20+
21+
```text
22+
Hey guys, had an issue with eyaml this morning, everything is fine on puppetservers with the
23+
older agent 8.25.0-1+ubuntu24.04
24+
but on puppetservers with the newer agent 8.26.0-1+ubuntu24.04 (all on puppetserver 8.12.1-1+ubuntu24.04 )
25+
I'm seeing Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call,
26+
Function Load Error for function 'eyaml_lookup_key': Lookup using eyaml lookup_key function is only
27+
supported when the hiera_eyaml library is present
28+
29+
from a client agent.
30+
31+
hiera-eyaml is present on the server:
32+
```
33+
34+
Bug analysis showed that the base64 dependency declaration is needed for Ruby 3.4/4 because it moved from a default gem to a bundled gem, but 0.3 is too new for the default gem version in Ruby 3.2, so it caused issues in OpenVox 8.
35+
36+
The community reacted and fixed the bug with the following commits:
37+
38+
- [hiera-eyaml - April 15 2026 at 7:15 PM CEST](https://github.com/voxpupuli/hiera-eyaml/commit/cd64af6580b9d2e30d6b90bf78c442f4db711b1e)
39+
- [puppet-runtime - April 15 2026 at 10:32 PM CEST](https://github.com/OpenVoxProject/puppet-runtime/commit/75960a166fe1eb203e2c88c463ce65a9901963ed)
40+
- [openvox - April 15 2026 at 11:01 PM CEST](https://github.com/OpenVoxProject/openvox/commit/1a4c6ae5006242df50c6d26a94214c7d1f4361fb)
41+
- [openvox tag - April 16 2026 at 1:08 AM CEST](https://github.com/OpenVoxProject/openvox/commit/06930e46fcad68fa0a6e29afd4fbf36569dddab8)
42+
43+
The new release [8.26.1](https://github.com/OpenVoxProject/openvox/releases/tag/8.26.1) was available on April 15 2026 at 1:11 AM CEST.
44+
45+
The packages of this new release were available on the repository server on April 15 2026 at 1:22 AM CEST.
46+
47+
That's less than 8 hours from release to bug identification to fixed release.
48+
49+
That is less time compared to the sun being visible in Europe on that day (6:07 AM CEST to 8:07 PM CEST).
50+
51+
The Vox Pupuli community has proven that automation is the key to success.
52+

0 commit comments

Comments
 (0)