Redmine

There is currently a package in bookworm (currently in testing) and in buster-backports (as stable as it gets).

Unless there are further significant changes in Debian's supported library versions (such as the supported Rails or Ruby versions) until bookworm becomes stable, A Redmine package will likely be included in bookworm propper. However, this is not something the Redmine project can actually influence since this heavily depends on the Ruby ecosystem and packaging rules within Debian. For an authorative reply on this matter, you likely have to ask the Debian package maintainers using the right channels within the Debian project.

Dear Holger,

thank you for your information.

Yours, Markus

This involves a bit of effort from both sides, both the application developers and the package maintainers in Debian

Some software is very hard for distributions to support.

If the developers of a Ruby application, for example, Redmine, make a conscious effort to avoid using bleeding edge libraries then it will always be easier to support in distributions.

By comparison, in reSIProcate, we would like to use some C++17 features but we avoid them and only use C++11. Using C++11, we ensure people can still compile our code on some slightly dated platforms like Red Hat 8 and even Red Hat 7.

Another example is adding new libraries. Whenever I update the asio dependency in reSIProcate, I look at which version of the asio library is available in Debian, Ubuntu, Fedora and Red Hat (EPEL). If I want to use a completely new library, I make a package of the library for both Debian and Fedora.

All this takes a bit more time and commitment from both sides. This is one reason I raised the topic about crowdfunding:
https://www.redmine.org/boards/1/topics/67289

Funding is one way to show appreciation for the people who are doing this work.