One issue is it might be hard to ensure we don't have regressions. We rely on
GitHub CI for automated regression testing, and that only supports up to Windows
Server 2022 (which I believe is based on Windows 10). It sounds like Windows
Server 2025 will be based on Windows 11, but that's in preview and not available
on Github CI yet.
If we wanted to officially support it, we might want to make sure we have a plan
to do manual testing periodically, or at least prior to a release. Or we could
wait until Windows Server 2025 is released and GitHub Actions supports it.
On 2024-09-12 04:26 PM, Mike Beckerle wrote:
Windows 11 has been out since Oct 2021.
We currently test on Windows 10 only
Do we need to add Windows 11?
Windows 11 is *finally* a fully unicode-enabled system so I have read.
Windows 10 is not. Standard USA-configured Windows 10 installs still
are using an 8-bit charset by default for command line work, hence,
we've had to advocate that people install the Japanese language pack
which upgrades the fonts and charset defaults to be unicode capable.
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
