Is PSU being abandoned ?

Hey @krisr ,

PSU is very much alive!

While you haven't seen me as much, I still very much working on PSU every day. We are, and have been, in the process of onboarding more folks to help take over or assist in many of the roles I was performing myself. This means working with teams like development, support, sales and marketing. It also means onboarding teams we didn't have before like security and quality assurance. As you can imagine, this is very time consuming for me but an investment in PSU's future. I'm beginning to get some head space back to get more involved in the PSU community once again. You'll see me hosting the new PSU Community Call, attending events like PSConfEU and being active on here and Discord.

I know there haven't been many cool features in the past few months. This doesn't mean development has slowed down. We actually have many more folks contributing to the PSU source repository than ever before. We've had to focus on some transitional pieces, like a new build and release pipeline and licensing. We've also been working on some foundational pieces like better automated testing, security fixes found during audits and working through the back log of bugs and quality of life improvements.

We are working on aligning with Devolutions' release schedule so you will be seeing 2026.2 soon and we will be announcing those features at PSConfEU. I have a talk dedicated to it. We've been hard at work on those for the last few months as well. I will be the first to admit that we have had more bugs than I would like, but we're working on improving that through more thorough manual and automated testing to catch issues before they go out the door. We're doing the same with security reviews and it's leading to more secure code as a result. PSU has always been a very complicated product to test and it was, honestly, becoming increasingly difficult to manage by myself before joining Devolutions. While code quality is not something that happens immediately, it's a central focus of what we are doing.

As for the GitHub issue tracker move and new community being quiet, I wouldn't worry about that too much. We've already migrated all the GitHub issues into our internal Jira tracker and have started to prioritize them. We're still trying to figure out what we put into the new forum for those or whether we just let the new forum start to collect new items. The forum itself actually integrates with all our internal tooling so it is way more streamlined than before. Users can still request features and report bugs and we can automatically create tickets to work on those items. When they are released, the forum topics will be updated accordingly. The forum is also quiet since it's only been a week since we switched over. We are still fixing links to it and ensuring people know where it is so it's probably going to take a bit for it to bounce back to previous activity. Eventually, we will redirect from the old forum to the new one and have proper links in the product itself.

I hope that helps understand what's happening with PSU. Devolutions is very much invested. I'm still leading the charge.

Thank you for the transparency @Adam Driscoll I can't imagine how much work it is to merge with another company. I really liked the transparency of the GitHub issues to be able to find bugs that others have reported as well as learning about new things people are using psu for. There is a lot of good information you can get about a product based on how others are using it. That feature also helped involve the community about what was changing and what new features were being worked on.