Skip to content

Commit ad4f84e

Browse files
committed
Added articles about 4.2.2 release and packaging.
1 parent 0ce108f commit ad4f84e

File tree

2 files changed

+34
-0
lines changed

2 files changed

+34
-0
lines changed
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: "Packaging OFT for Distributions"
3+
date: "2026-02-07T13:51:53+01:00"
4+
draft: false
5+
author: sebastian
6+
---
7+
8+
Our next goal is to get OFT packaged for easier installation. We will start with Debian and RPM packages soon. Ultimately, we would like to get OFT shipped with the popular distributions. This will probably help with the adoption. But until that happens, it will be a long way.
9+
10+
By the way, if you read this and are a curious developer with experience in the Apple ecosystem, we are looking for help with packaging OFT for macOS. If you are interested, please reach out to us.
11+
12+
The same goes for Windows packaging. We are a bunch of Unix nerds and could use some help in that area.
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: "Release 4.2.1"
3+
date: "2026-02-07T13:31:41+01:00"
4+
draft: false
5+
author: sebastian
6+
---
7+
8+
> Everything that can go wrong will go wrong.
9+
10+
*Ed Murphy* (not really, the original quote was a bit different)
11+
12+
## Release 4.2.2 (or the moment we found out 4.2.1 was not on Maven Central)
13+
14+
Finally, we managed to get a new release of OFT out of the door.
15+
16+
While [4.2.2](https://github.com/itsallcode/openfasttrace/releases/tag/4.2.2) is only a bugfix and security release, it also inherits a new feature from 4.2.1. Why do I mention that?
17+
18+
Because it turns out that we had a problem with our Maven Central deployment and 4.2.0 was never properly released.
19+
20+
Generally, my observation is that release pipelines have become more and more complex over time. Some of that we owe to repeated supply chain attacks on package repositories. This is why we can't have nice things. But I digress.
21+
22+
The new feature is peeking into XML files before treating them as OFT input. Only if the header looks like a ReqM2 file, OFT will process it. This speeds up scanning of larger projects and removes warnings that came up when OFT tried to read a non-ReqM2 file.

0 commit comments

Comments
 (0)