In jPOS 3.0.2 we are moving fast—very fast
Alejandro Revilla
In jPOS 3.0.2, we are moving fast—and that speed comes with trade-offs. As we iterate and improve the platform, some functionality may change or, in certain cases, break.
I’m writing this while working on a long-overdue feature in jPOS: full DataSet support (TLV and DBM) for ISO8583 v2003:2023 messages. This change will break existing cmf.xml configurations. The good news is that preserving the current behavior is straightforward—we’ll document it in the upcoming PR and blog post (in short: you can vendor your existing cmf.xml).
Still, this is a good example of the kind of change that can catch you off guard if you’re not closely following what’s happening. At the current pace, we need better communication loops—otherwise, it’s very easy for your codebase to drift into obsolescence.
To minimize disruption and ensure we’re aligning with real-world use cases, we strongly encourage you to stay engaged with the community. If you rely on specific features, integrations, or workflows, now is the time to make your voice heard.
This message is going to a large audience—over 2000 subscribers—and we know many of you have been silent. In some cases, that silence may come from hesitation or past experiences that didn’t feel entirely welcoming. We want to be clear: your questions, use cases, and feedback are important, and we encourage you to participate. A healthy community depends on open, respectful dialogue, and we are committed to fostering that environment.
Your input helps us understand what matters most, prioritize stability where it’s needed, and avoid unintentionally dropping support for functionality that is still in use. Silence makes it harder for us to distinguish between unused features and essential ones.
We’ve also been actively updating our website and blog, and—most importantly—our tutorials. New content is being added on a daily basis, so it’s worth checking in regularly to stay up to date with the latest changes and best practices.
For ongoing discussions, the mailing list remains the preferred channel. For more immediate, ad-hoc questions, the #support channel on Slack is the best place to get help in real time.
If you need to reach out directly, my X (@apr) has DMs open, and I’m also available via email or LinkedIn or email.
We’re moving quickly—but we want to move in the right direction, with you.