Just a few weeks after previous release, ejabberd 25.04 is published with an important security fix, several bug fixes and a new API command.

Release Highlights:

• Fix handling multiple occupant-id
• Kick_users API command

If you are upgrading from a previous version, there are no changes in SQL schemas, configuration, API commands or hooks.

Other contents:

• Acknowledgments
• Improvements in ejabberd Business Edition
• ChangeLog
• ejabberd 25.04 download & feedback

Below is a detailed breakdown of the improvements and enhancements:

mod_muc_occupantid: Fix handling multiple occupant-id

Fixed issue with handling of user provided occupant-id in messages and presences sent to muc room. Server was replacing just first instance of occupant-id with its own version, leaving other ones untouched. That would mean that depending on order in which clients send occupant-id, they could see value provided by sender, and that could be used to spoof as different sender.

New kick_users API command

There is a new API command kick_users that disconnects all the client sessions in a given virtual host.

Acknowledgments

We would like to thank the contributions to the source code, documentation, and translation provided for this release by:

• Travis Burtrum for reporting problem in occupant-id
• Marcos de Vera Piquero for the new kick_users API command
• Besnik Bleta , updated the Albanian translation
• Sketch6580 , updated the Chinese translation
• Nautilusx , updated the German translation
• Silvério Santos , updated the Portuguese translation
• Wellington Uemura , updated the Portuguese (Brazil) translation
• Максим Горпиніч , updated the Ukrainian translation

And also to all the people contributing in the ejabberd chatroom, issue tracker...

Improvements in ejabberd Business Edition

For customers of the ejabberd Business Edition , in addition to all those improvements and bugfixes:

• Bugfix on max_concurrent_connections for mod_gcm , mod_webhook and mod_webpush

ChangeLog

This is a more complete list of changes in this ejabberd release:

Security fixes

• mod_muc_occupantid : Fix handling multiple occupant-id

Commands API

• kick_users : New command to kick all logged users for a given host

Bugfixes

• Fix issue with sql schema auto upgrade when using sqlite database
• Fix problem with container update, that could ignore previous data stored in mnesia database
• Revert limit of allowed characters in shared roster group names, that will again allow using symbols like :
• Binary installers and ejabberd container image: Updated to Erlang/OTP 27.3.2

Full Changelog

https://github.com/processone/ejabberd/compare/25.03...25.04

ejabberd 25.04 download & feedback

As usual, the release is tagged in the Git source code repository on GitHub .

The source package and installers are available in ejabberd Downloads page. To check the *.asc signature files, see How to verify ProcessOne downloads integrity .

For convenience, there are alternative download locations like the ejabberd DEB/RPM Packages Repository and the GitHub Release / Tags .

The ecs container image is available in docker.io/ejabberd/ecs and ghcr.io/processone/ecs . The alternative ejabberd container image is available in ghcr.io/processone/ejabberd .

If you consider that you&aposve found a bug, please search or fill a bug report on GitHub Issues .

With ejabberd 25.03 , the Matrix gateway ( mod_matrix_gw ) now supports not only one-to-one chats, but also joining Matrix rooms via XMPP. That’s right — your favorite XMPP client can now talk to Matrix users or hop into Matrix rooms just like regular MUCs. ✨

In this guide, we’ll show a quick demo of:

1. One-to-one chat between an XMPP and a Matrix user.
2. Joining a Matrix room and chatting from your XMPP client.

And the best part? You don’t need to install a Matrix client at all. Keep your favorite XMPP client near, welcome to the magic of federation & interoperability.

---

🛠 Setup Summary

We won’t repeat the full configuration steps here — they’re already covered in this earlier blogpost and the 25.03 release note .

In short, you’ll need:

• A properly configured ejabberd server with mod_matrix_gw
• Block outgoing connections to lethe.matrix.org to avoid conflicts with their XMPP instance

Here’s a minimal config snippet:

listen:
  -
    port: 8448
    module: ejabberd_http
    tls: true
    request_handlers:
      "/_matrix": mod_matrix_gw

modules:
  mod_matrix_gw:
    key_name: "xxxxxx"
    key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    matrix_id_as_jid: true

Wondering what is the Matrix signing key? Please refer to previous blog post: Matrix gateway setup with ejabberd

Still not sure if your setup is correct? Try Matrix Federation Tester to check if everything is wired up properly.

🧪 One-to-One Chat (XMPP ↔ Matrix)

In your XMPP client (e.g. Psi), add a Matrix contact using this format:
matrixUser%theirMatrixServer.tld@yourXMPPserver.tld

In my case, that means:
adrien-p1%matrix.org@matrix.mickael.m.in-app.io

On the Matrix side (e.g. Element Web), your contact will get a request. Once accepted, you’re good to chat!

✅ Demo: XMPP user (Psi) chats with Matrix user (Element Web)

🧪 Join a Matrix Room from your XMPP Client

Alright, let’s join a public Matrix room now.

From your XMPP client, you can join any Matrix public room using this format:
#matrixRoom%theirMatrixServer.tld@yourXMPPserver.tld

We’ll use the following room: #ejabberd-demo:matrix.org , so in my case, that means joining:
#ejabberd-demo%matrix.org@matrix.mickael.m.in-app.io

Once connected, you’ll be able to send and receive messages from any other participant, just like in a regular MUC. :)

✅ Demo: Join and chat in a Matrix room from XMPP

🐞 Known Caveats

There&aposs still a lot of work to do to make it seamless, here&aposs a short list of currently known caveats:

• Room presence can be overwhelming in large rooms (thousands of Matrix users may appear "online").
• No E2EE support between Matrix and XMPP — encryption must be disabled for now.
• If the server restarts, 1-to-1 conversations must be restarted (re-added), as persistence is not implemented yet.
• Only Matrix room protocol versions 9, 10, and 11 are supported.

🧵 Wrapping Up

With this, ejabberd makes another step into being a powerful bridge into the Matrix federation, for both private and public communication.

It’s a great way to keep using your favorite XMPP tools while staying connected to Matrix communities.

Got feedback? Drop us a line in the comments or open a PR .

Happy bridging! 🙌

Dino is a secure and open-source messaging application. It uses the XMPP (Jabber) protocol for decentralized communication. We aim to provide an intuitive and enjoyable user interface.

The 0.5 release improves the user experience around file transfers and includes two completely reworked dialogs.

Improved file sharing

The way file transfers are currently done in the XMPP ecosystem is limited in functionality and files can sometimes be received out-of-order. Dino now supports a new method for announcing file transfers ( XEP-0447 ), which solves this issue. Additionally, users can now see preview images or other file details before downloading the file. Dino currently only uses the new method for unencrypted file transfers, for example in public channels. Encrypted file transfers will also support the new protocol once Dino supports full-stanza encryption. All file transfers now also display the upload or download progress.

Reworked dialogs

The account and preferences dialogs have been combined into a single, new dialog. This dialog lets you manage accounts and adjust encryption and other settings. It now also includes some new settings like an option for OMEMO encryption by default, which is enabled by default.

Additionally, the conversation details dialog has been completely redesigned. Both dialogs are now fully compatible with mobile devices.

Colors and more

Dino now uses the same fallback avatar colors as other clients ( XEP-0392 ), creating a more consistent experience across applications.

A new unread line has been added, indicating the point up to which you’ve already read the messages.

Dino has also switched from CMake to Meson, which allows for an easier development process.

Alentejo

We named this Dino release “Alentejo” after a region in Portugal.

Alentejo is a region in southern Portugal that is known for its wide plains that are dotted with wineyards and cork trees. The region has a Mediterranean climate with summers regularly reaching temperatures above 40 degrees.

Currently, about 3.6% of all deaths in the region are caused by heat. Heatwaves, in particular, pose a serious health risk and are expected to become more frequent and severe due to global warming [ 1 ]. If CO₂ emissions keep increasing, heat-related deaths could make up 15.8% of all deaths in the region by 2100. However, if action is taken to combat climate change, this number could be limited to 6.6% [ 2 ].

The IgniteRealtime community is happy to announce releases for two of its projects! Both are for XMPP-libraries that we produce.

Tinder is a Java based XMPP library, providing an implementation for XMPP stanzas and components. Tinder’s origins lie in code that’s shared between our Openfire and Whack implementations. The implementation that’s provided in Tinder hasn’t been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality.

The v2.1.0 release of Tinder is a maintenance release. It updates various libraries that are used by Tinder, and removes deprecated, unused code. Tinder now requires Java 11 or later. The full list of changes in this release can be found in the release notes .

Whack is a Java library that easily allows the creation of external components that follow the XEP-0114: Jabber Component Protocol. This library allows you to create server-sided components of your XMPP network that can run as stand-alone processes. That’s particularly useful when you are creating functionality for which scalability configuration differs from that of Openfire, or if you want to re-use your component for XMPP servers other than Openfire!

The v3.0.0 release of Whack is a maintenance release. It improves reconnection logic (when connection to the XMPP server is lost), it no longer ships with an embedded webserver (that was old, unused, and was raising vulnerability warnings, and updates some libraries (such as Tinder) to more recent versions. The fulll list of chagnes in this release can be found in the release notes .

We would love to hear from you! If you have any questions, please stop by our community forum or our live groupchat .

For other release announcements and news follow us on Mastodon or X

1 post - 1 participant

Read full topic

Elixir is a lightweight, high-performance programming language built on the Erlang virtual machine. It’s known for its simple syntax and efficient use of digital resources. But how does this translate to business benefits?

Elixir is already powering companies like Discord and Pinterest. It helps businesses reduce costs, improve process efficiency, and speed up time to market.

Here are five reasons why Elixir is a game-changer for your business.

1. Cleaner Code, Faster Progress

Elixir is designed for simplicity. Its clean syntax and functional style help developers write concise, readable code, with fewer bugs and less overhead.

For teams, this means faster development cycles and smoother collaboration. For businesses, it means shorter time to market and reduced long-term maintenance costs, which is especially useful during talent shortages.

Projects move faster when your team isn’t fighting complexity.

2. Built-In Concurrency, Built-In Stability

Concurrency – the ability to run multiple tasks at once -is essential for modern applications. Elixir handles this natively, thanks to the Erlang virtual machine it runs on.

With Elixir, you can run millions of lightweight processes simultaneously . It’s ideal for:

• Real-time systems (e.g., messaging, live data feeds)
• Applications with high user demand
• Businesses that can’t afford downtime

Crucially, these processes run independently. If one fails, the rest carry on — making your application more resilient by design.

3. Smarter Use of Resources

Elixir is resource-efficient. As your infrastructure scales, Elixir adapts automatically using the processing power available.

This has clear benefits:

• No wasted server capacity
• Better app performance on existing infrastructure
• Lower hosting and scaling costs

Your tech stack runs leaner and more efficiently, with fewer surprises at scale.

4. Elixir means simple scalability

Elixir was made for scalable systems. Its lightweight processes and distributed architecture allow your application to grow without rewriting core components.

What sets it apart:

• Seamless horizontal scaling across machines
• High fault tolerance through process isolation
• Built-in support for distributed systems

This makes Elixir especially strong for digital products that need to scale quickly or support unpredictable usage.

Take Bleacher Report . They switched from Ruby to Elixir and saw results:

• Server count dropped from 150 to 8
• The app now handles over 200 million push notifications a day
• Performance improved, with far fewer bottlenecks

All of this was achieved while reducing infrastructure overhead.

Read the full case study here .

Modern Tools for Modern Challenges

Elixir isn’t just fast it’s current.

It supports distributed teams, integrates with today’s tools, and works well alongside other languages and frameworks.

It’s especially useful for:

• Products that need to ship fast and scale cleanly
• Teams juggling real-time features, analytics or event-driven systems
• Organisations focused on reliability and long-term performance

Unlike many programming languages, Elixir is both powerful and practical.

To conclude

Elixir helps teams move quickly, handle growth with ease, and build reliable systems without unnecessary complexity. For modern businesses building digital platforms, it’s a quiet powerhouse and a strong strategic choice.

Want to learn more about Elixir? Explore the full “What is Elixir?” post .

Want to discuss how Elixir can enhance your business performance? Get in touch with the team.

The post Elixir for Business: 5 Ways It Transforms Your Processes appeared first on Erlang Solutions .

This release brings an all-new activity feed and adds support for Message Displayed Synchronization across group chats. Thank you for all your contributions!

What’s New

Gajim 2.1 comes with a new page called ‘Activity feed’. Currently, it displays events around group chat invitations, contact requests, and updates. Clicking an event allows you to act on it (e.g. accept an invitation) A badge indicates new activities on the top left corner of Gajim’s window. This will be the central feed for all kinds of activities in the future (e.g. reactions, replies, mentions, message reminders).

If you have more than one account enabled in Gajim, accounts will now be displayed inside a menu available at the bottom left corner of the window. A left click brings you to your account, while a right click allows your to set your status.

When following large group chats across multiple devices, you’ve probably experienced this: You read all new messages on one device, and later you switch to another device, but all those messages you’ve already read are now shown as unread messages. Seeing if you have read messages on another device is now supported by Gajim through XEP-0490: Message Displayed Synchronization . This feature is also supported by Conversations on Android for example. Thanks @nicoco for contributing to this feature!

A note for Windows users: At the time of writing, there are some issues with emoji rendering on Windows. That’s why there is no release of Gajim 2.1 for Windows yet. This issue should soon be resolved and we will post an update once Gajim 2.1 is released on Windows.

More Changes

• Status icon: Fixed showing menu correctly
• Emoji chooser: Fixed segfault after choosing emoji, which occurred on some systems
• Nickname: Fixed displaying published nickname correctly
• Start chat: Added ‘Execute Command…’ menu item
• Removed unread message confirmation dialog at shutdown

And much more! Have a look at the changelog for a complete list.

As always, don’t hesitate to contact us at gajim@conference.gajim.org or open an issue on our Gitlab .

XMPP Newsletter Banner

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of March 2025.

Like this newsletter, many projects and their efforts in the XMPP community are a result of people’s voluntary work. If you are happy with the services and software you may be using, please consider saying thanks or help these projects! Interested in supporting the Newsletter team? Read more at the bottom .

XSF Announcements

The XMPP Standards Foundation published an Open Letter to urge Meta to adopt XMPP for messaging interoperability. It’s time for real interoperability. Let’s make it happen.

XSF Membership

If you are interested in joining the XMPP Standards Foundation as a member, please apply until May 18th, 2025, 00:00 UTC! .

XSF Fiscal Hosting Projects

The XSF offers fiscal hosting for XMPP projects. Please apply via Open Collective . For more information, see the announcement blog post . Current projects you can support:

• Mellium Co-op
• Bifrost bridge
• Prav iOS
• diasp.in

XMPP Events

• XMPP Track at FOSSY : Call for proposals is open until April 28th 2025! Once again this year, the soprani.ca project is pleased to announce its annual offer for funding to the potential attendees who may be struggling with financial limitations, especially to those who would like to give an XMPP related talk. Please, join us at discuss@conference.soprani.ca , and don’t hesitate to ask for more information.
• Berlin XMPP Meetup [DE / EN]: monthly meeting of XMPP enthusiasts in Berlin, every 2nd Wednesday of the month at 6pm local time.
• XMPP Italian happy hour [IT]: monthly Italian XMPP web meeting, every third Monday of the month at 7:00 PM local time (online event, with web meeting mode and live streaming).
• XMPP Sprint in Berlin : On Friday, 23rd, Saturday, 24th, and Sunday, 25th of May 2025.

Talks

• SASL-HT (The Hashed Token SASL Mechanism) was presented by Florian Schmaus at the 122nd meeting of the Internet Engineering Taskforce (IETF) . A recording is available on YouTube and the slides are available at the IETF 122 website . If adopted, this draft will become a “Request For Comments” (RFC) that will help standardize fast XMPP client reauthentication methods such as the one specified by XEP-0397 . The draft will be discussed further on the IETF Kitten working Group mailing list .

XMPP Articles

• Installer son serveur XMPP avec Prosody by Codimp has been updated to reflect the changes introduced by the latest Prosody 13.0.0 release [FR]
• Kaidan 0.12.0: User Interface Polishing and Account Migration Fixes by melvo for Kaidan IM .
• It’s time for real interoperability. Let’s make it happen! by guus for the Ignite Realtime News .
• Supporting XMPP Standard Foundation’s open letter to Meta for true interop by ProcessOne .
• Monocles , the project responsible for the XMPP Monocles chat Web and Android clients, started a crowdfunding campaign . The main goal is to create a platform where privacy, digital sovereignty and sustainability take center stage. Your privacy is non-negotiable. The funding period will span from 03.28.2025 to 06.30.2025.

XMPP Software News

XMPP Clients and Applications

• Gajim has released versions 2.0.1 , 2.0.2 , 2.0.3 and 2.0.4 with improvements and bug fixes. Head over to their News section for all the details.
• Kaidan has released versions 0.12.0 , 0.12.1 and 0.12.2 . These versions bring user interface polishing, account migration fixes, voice message and password change fixes, message removal and bubble fixes, along with more bugfixes. Check the changelog for each respective version here , here and here for all the details.
• Poezio has released versions 0.15.0 and 0.15.1 of their console XMPP client. Detailed information available on the release announcement .
• Profanity has released version 0.15.0 of their console based XMPP client. After more than a year and a half in the making, this release packages a large list of new features, improvements, bug fixes and more. You can find a detailed list of changes for this release on their changelog .
• prose-web-app has released versions 0.6.2 and 0.7.0 of its Web implementation of the Prose app.

XMPP Servers

• ProcessOne is pleased to announce the release of ejabberd 25.03 : a big release with new features and many improvements, as it comes three months and 180 commits after ejabberd 24.12.
• Prosody IM is pleased to announce the release of version 13.0.0 , the new major release of the Prosody XMPP server. This release brings a wide range of improvements that make Prosody more secure, performant, and easier to manage than ever before. Read about all the details on the release changelog . As always, detailed download and install instructions are available on the download page for your convenience.

XMPP Libraries & Tools

• go-xmpp versions 0.2.11 and 0.2.12 have been released.
• libstrophe version 0.14.0 has been released.
• peertube-plugin-livechat version 12.0.3 has been released.
• pelican-pubsub has been released. This is a plugin for the Pelican publishing system that implements support for Atom Over XMPP, through XMPP pubsub, enabling direct interaction (like publishing or adding comments) with Libervia and Movim users via XMPP.
• prose-core-client versions 0.1.101 and 0.1.102 have been released.
• python-nbxmpp versions 6.0.1 and 6.0.2 have been released.
• QXmpp versions 1.10.2 and 1.10.3 have been released.
• Slidge version 0.2.8 has been released.
• Slixmpp versions 1.9.1 and 1.10.0 have been released. You can read the respective release announcements here and here for all the details.

Extensions and specifications

The XMPP Standards Foundation develops extensions to XMPP in its XEP series in addition to XMPP RFCs . Developers and other standards experts from around the world collaborate on these extensions, developing new specifications for emerging practices, and refining existing ways of doing things. Proposed by anybody, the particularly successful ones end up as Final or Active - depending on their type - while others are carefully archived as Deferred. This life cycle is described in XEP-0001 , which contains the formal and canonical definitions for the types, states, and processes. Read more about the standards process . Communication around Standards and Extensions happens in the Standards Mailing List ( online archive ).

Proposed

The XEP development process starts by writing up an idea and submitting it to the XMPP Editor . Within two weeks, the Council decides whether to accept this proposal as an Experimental XEP.

• No XEPs proposed this month.

New

• Version 0.1.0 of XEP-0503 (Server-side spaces).
  • Promoted to Experimental (XEP Editor: dg)

Deferred

If an experimental XEP is not updated for more than twelve months, it will be moved off Experimental to Deferred. If there is another update, it will put the XEP back onto Experimental.

• No XEPs deferred this month.

Updated

• No XEPs updated this month.

Last Call

Last calls are issued once everyone seems satisfied with the current XEP status. After the Council decides whether the XEP seems ready, the XMPP Editor issues a Last Call for comments. The feedback gathered during the Last Call can help improve the XEP before returning it to the Council for advancement to Stable.

• No Last Call this month.

Stable

• No XEPs moved to Stable this month.

Deprecated

• No XEPs deprecated this month.

Rejected

• No XEPs rejected this month.

Spread the news

Please share the news on other networks:

• Mastodon
• LinkedIn
• YouTube
• Lemmy instance (unofficial)
• Reddit (unofficial)
• XMPP Facebook page (unofficial)

Also check out our RSS Feed !

Looking for job offers or want to hire a professional consultant for your XMPP project? Visit our XMPP job board .

Newsletter Contributors & Translations

This is a community effort, and we would like to thank translators for their contributions. Volunteers and more languages are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

• English (original): xmpp.org
  • General contributors: Adrien Bourmault (neox), Alexander “PapaTutuWawa”, Arne, Benson Muite, cal0pteryx, emus, Federico, Gonzalo Raúl Nemmi, Jonas Stein, Kris “poVoq”, Licaon_Kter, Ludovic Bocquet, Mario Sabatino, melvo, MSavoritias (fae,ve), nicola, Schimon Zachary, Simone Canaletti, singpolyma, XSF iTeam
• French: jabberfr.org and linuxfr.org
  • Translators: Adrien Bourmault (neox), alkino, anubis, Arkem, Benoît Sibaud, mathieui, nyco, Pierre Jarillon, Ppjet6, Ysabeau
• Italian: notes.nicfab.eu
  • Translators: nicola
• Spanish: xmpp.org
  • Translators: Gonzalo Raúl Nemmi
• German: xmpp.org
  • Translators: Millesimus

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Each month’s newsletter issue is drafted in this simple pad . At the end of each month, the pad’s content is merged into the XSF GitHub repository . We are always happy to welcome contributors. Do not hesitate to join the discussion in our Comm-Team group chat (MUC) and thereby help us sustain this as a community effort. You have a project and want to spread the news? Please consider sharing your news or events here, and promote it to a large audience.

Tasks we do on a regular basis:

• gathering news in the XMPP universe
• short summaries of news and events
• summary of the monthly communication on extensions (XEPs)
• review of the newsletter draft
• preparation of media images
• translations
• communication via media accounts

Unsubscribe from the XMPP Newsletter

To unsubscribe from this list, please log in first . If you have not previously logged in, you may need to set up an account with the appropriate email address.

License

This newsletter is published under CC BY-SA license .

We are pleased to announce a new minor release from our stable branch.

As is the tradition with software, here is our first patch release following shortly behind our major 13.0.0 release announced a few weeks ago. It fixes some important bugs that were discovered after the release.

Many thanks to everyone who reported issues and helped with testing the fixes for this release. We appreciate it!

For those of you on 0.12.x who haven’t upgraded yet, skip 13.0.0 and jump straight to 13.0.1 if you can. It will be a smoother upgrade.

A summary of changes in this release:

Fixes and improvements

• mod_admin_shell: Add debug:cert_index() command to aid debugging of automatic certificate selection
• mod_tls: Enable Prosody’s certificate checking for incoming s2s connections (fixes #1916 : Impossible to override certificate verification policy in 13.0)
• portmanager: Multiple fixes to use correct certificates for direct TLS ports (fixes #1915 )
• net.server_epoll: Use correct connection timeout when initiating Direct TLS
• mod_roster: Fix shell commands when a component is involved (fixes #1908 : error in prosodyctl shell roster attempting to subscribe a component)
• mod_http_file_share: Explicitly reject all unsupported ranges
• mod_http_file_share: Fix off by one in Range response
• mod_admin_shell, prosodyctl shell: Report command failure when no password entered (fixes #1907 : prosodyctl adduser: unexpected account creation on password mismatch)

Minor changes

• mod_storage_sql: Drop legacy index without confirmation to ease upgrades
• util.adminstream: Fix traceback on double-close (fixes #1913 : Prosody fails to completely stop while shell watch:log is active)
• certmanager: Improve logging for all cases where certs are skipped
• mod_tls: Collect full certificate chain validation information
• mod_s2s: Fix error detection with newer versions of OpenSSL
• portmanager: Add debug log message to state which certificate we end up using
• prosodyctl check certs: Use correct hostname in warning message about HTTPS
• prosodyctl check: Be more robust against invalid disco_items, and show warning
• spec/tls: Add TLS/certificate integration tests
• mod_http_file_share: Improve error reporting by using util.error more
• core.storagemanager: Fix tests by removing an assert that upset luarocks
• core.usermanager: Fix COMPAT layer for legacy is_admin() function
• certmanager: Remove obsolete and verbose index log (replaced by shell command)
• doap: Add XEP-0333, XEP-0334, XEP-0156 and mod_http_altconnect

Download

As usual, download instructions for many platforms can be found on our download page

If you have any questions, comments or other issues with this release, let us know!

Our project creates a framework that allows anyone to easily add XMPP standards compliance tests to the test phase of their build pipeline. Prior to our most recent release (version 1.5.0) a test execution would basically run all tests in the test suite. We provided an option to exclude certain tests, but in essence, the bulk of tests would execute.

This behavior is generally preferable when testing an XMPP server implementation. A benefit of exclusion-based configuration is that tests that are newly added to the test suite will automatically be picked up, without requiring a configuration change.

However, there are scenarios where it is desirable to execute only a specific set of tests, for example when:

• testing of a server-sided component, that implements only one specification, or
• testing a development branch in which changes are applied to only one feature.

In those scenarios, having to disable all other tests is cumbersome.

We have now made available a mechanism in which specific tests can be included . When you include tests, only the included tests are executed. These configuration is very similar to that of the exclusion of tests. You can find more information in our documentation on Selecting Tests .

Please let us know if you like the new features. We’d love to hear from you!

• Splash image courtesy of Heeren Darji, Unsplash