Shaping the Roadmap for jPOS 3.0.2
8 views
Skip to first unread message
Alejandro Revilla
Jan 8, 2026, 7:52:18 AM (4 days ago) Jan 8
to jPOS Users
As we approach the release of jPOS 3.0.1 (see ChangeLog), it is a good time to invite you to help shape the roadmap of the next release, 3.0.2. In the past, we had a very active jpos-dev mailing list, and we made the mistake of splitting it into jpos-dev for development roadmap discussions and jpos-users for user questions and support. That was a mistake, because conversations became scattered.
In the next release, we plan to continue the work started on Structured Logging, distributed tracing, and observability, as well as adding some missing features required by ISO-8583 v2003/2023 DataSets that are currently handled as opaque fields.
Regarding observability, we have instrumented the system using Micrometer (see the jPOS Monitoring project), but there is still a lot of additional instrumentation to perform.
At Transactility, we have our fair share of contact with very large production systems, and that is a great way to feel firsthand the pain points and requirements. However, the beauty of open source—and what makes it so powerful—is its massive distribution. There are thousands and thousands of jPOS deployments out there, and we want to hear about your pain points. Sometimes users go to great lengths, extending and massaging the jPOS library with bytecode instrumentation, just to achieve something that we could make much easier by, for example, changing a method from private to protected. Very simple things like that—we are eager to do them, and they often take us 30 seconds.
This post is a call for participation. Get in touch here, or, if you prefer, on Slack, where the core team is online most of the time. We have four interesting channels and close to 1000 members:
- #general for general discussions and announcements
- #commits, a good way to stay on top of commits, branches, issues, and discussions
- #support for almost real-time support when you are coding and hit a roadblock
- #jobs for job postings and for-hire announcements
Here is the Slack invite link. You are welcome to join!
Finally, my annual shameless request for a GitHub star, which you can give us on the Github repo.
@apr
In the next release, we plan to continue the work started on Structured Logging, distributed tracing, and observability, as well as adding some missing features required by ISO-8583 v2003/2023 DataSets that are currently handled as opaque fields.
Regarding observability, we have instrumented the system using Micrometer (see the jPOS Monitoring project), but there is still a lot of additional instrumentation to perform.
At Transactility, we have our fair share of contact with very large production systems, and that is a great way to feel firsthand the pain points and requirements. However, the beauty of open source—and what makes it so powerful—is its massive distribution. There are thousands and thousands of jPOS deployments out there, and we want to hear about your pain points. Sometimes users go to great lengths, extending and massaging the jPOS library with bytecode instrumentation, just to achieve something that we could make much easier by, for example, changing a method from private to protected. Very simple things like that—we are eager to do them, and they often take us 30 seconds.
This post is a call for participation. Get in touch here, or, if you prefer, on Slack, where the core team is online most of the time. We have four interesting channels and close to 1000 members:
- #general for general discussions and announcements
- #commits, a good way to stay on top of commits, branches, issues, and discussions
- #support for almost real-time support when you are coding and hit a roadblock
- #jobs for job postings and for-hire announcements
Here is the Slack invite link. You are welcome to join!
Finally, my annual shameless request for a GitHub star, which you can give us on the Github repo.
@apr
Reply all
Reply to author
Forward
0 new messages