Back on Track - with new Patch Kit in the way

Hey there, hope you're doing very well. The long-time absence from the website led to significant delay of OpenXP development, although our Discord members are aware about development of vNext counterpart of OpenXP, and of bigger patch kit preparations!

What's vNext?

vNext is a code name for any upcoming release of OpenXP, which stands out for differentiating between master and current trunk. The master consists of stable and production-ready changes, which are tested by developers team and ready for being included in the patch kit, so your source code will be always updated and the fixed versions of the progress won't break anything.

Code-name: Junewind

Junewind is a handy code name of the June 2026 patch kit release. You can follow it's development on our Codeberg repository, where you can see stuff introduced in Pre-release builds slowly materializing in the publicity, by the way introducing such changes as:

• Windows Research Kernel,
• Compilers update,
• Fixes on source code to prevent caveats on the way.

Currently, the Junewind is standing on Beta 1, meaning that there obviously will be bugs and problems with your existing source code compilation. Your reports and pull requests to fix them will be very helpful for us to make patch kit alive and stable for the release, among with bringing very meaningful improvements over Windows Server 2003 source code. Especially the Windows Research Kernel inclusion significantly improves kernel system and phases out of RTM version, creating a very good foundation for OpenWin and many other projects which will re-evaluate OpenXP not only as a project improving Windows Server 2003, but also giving a relatively new imagination about Windows XP and Server 2003 as you may think out.

Junewind will gradually receive it's bugfixes and continuous integration of AMD64 in it's fullest. If you apply this version of patch kit, you should be aware that this version changes AMD64 compilers set too, and it will give you many compiler errors which we are aware of and working on their resolving too.

AI integration

But there's an important catch: OpenXP won't accept any AI-generated pull requests which are not reviewed by humans and contain unchecked and bloated source code. If you may notice, the canary branch of patch kit contained pull requests co-worked by Claude and that broke the canary branch by requiring modern version of Python which is not supported on older versions of Windows than Windows 10 or 8.1. We don't refuse that LLMs are greatly improved in code generation and co-working, and these instruments will unavoidably improve by time, but only vibe coding and 100% trust on AI-generated results are bringing to unforeseen consequences, such as source code compilation errors, breakage of existing facilities and lots of funny catches which were never been a thing before.

Thank you for understanding, stay in ;)