{"id":183471,"date":"2026-09-25T16:54:33","date_gmt":"2026-09-25T14:54:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/dostupna-sistema-upravleniya-versiyami-apache-subversion-1-15-0"},"modified":"2026-09-25T16:54:38","modified_gmt":"2026-09-25T14:54:38","slug":"apache-subversion-1-15-0-version-control-system-now-available","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/apache-subversion-1-15-0-version-control-system-now-available","title":{"rendered":"The Apache Subversion version control system 1.15.0 is available.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After more than six years since the last significant release, the Apache Software Foundation has published the release of the centralized version control system Subversion 1.15.0. <\/p>\n
Key improvements in Subversion 1.15: <\/p>\n
\n
A new mode of operation without caching the base revisions of all files on the local system (Pristines On Demand) has been added, allowing disk space usage to be reduced by up to 50% by downloading files from the server as needed. The trade-off for reduced disk space is increased network traffic and longer execution times for operations like diff and revert. Disabling caching may be beneficial when working with large repositories with rarely changing files, placing the working copy on the same host as the repository, and on systems with limited disk space and fast network connections.\n
A new format for storing working copies (Format 32) has been implemented, designed to operate without local caching. It allows for the simultaneous use of different versions of working copy formats, enabling the preservation of the format of previously created working copies without updating existing projects through the team 'svn upgrade'.\n
Support for streaming execution of 'svn checkout' and 'svn update' operations has been added, significantly improving performance and reliability. Instead of copying to a temporary directory and then parsing it, data is now written directly to the repository and working directories (instead of copying from the temporary directory, the file is saved in place under a temporary name and then atomically renamed).\n
A new build system based on the CMake toolset has been implemented, greatly simplifying the build process on Windows and integrating with the vcpkg package manager for automatic dependency loading. The old build system based on Autoconf continues to be used by default for all platforms except Windows. <\/ul>\n