18.4.0 released Sep 25, 2023
Quality control
Quality control
Each candidate for a Vely release must build successfully for a given Linux distribution and on its native architecture, without simulators or cross-compilers. A suite of functional tests (including bug fixes to prevent regressions) must run without errors; currently, there are 2021 such tests.

Vely is tested on following distros: archlinux_rolling, debian_11, debian_12, fedora_37, fedora_38, mageia_8, opensuse_tumbleweed, redhat_8, redhat_9, ubuntu_18, ubuntu_20, ubuntu_22 however it may work on other distros derived from this list (see installation page). Both builds and tests are automated to prevent gaps in coverage.

Valgrind and Google Address Sanitizer (ASAN) are used to help eliminate memory violations and leaks.

Vely documentation is automated to a good degree, with internal/external link checking, HTML/troff make and reference/index building.
See also
General
about-Vely  
application-architecture  
deploying-application  
how-vely-works  
quality-control  
rename-files  
SELinux  
vely-architecture  
vely-removal  
vely-version  
vf  
vv    
See all
documentation

You are free to copy, redistribute and adapt this web page (even commercially), as long as you give credit and provide a link back to this page (dofollow) - see full license at CC-BY-4.0. Copyright (c) 2019-2023 Dasoftver LLC. Vely and elephant logo are trademarks of Dasoftver LLC. The software and information on this web site are provided "AS IS" and without any warranties or guarantees of any kind.