Difference between revisions of "Wishlist"
(fix url) |
m |
||
| Line 18: | Line 18: | ||
== Per activity == | == Per activity == | ||
| − | == Development == | + | === Development === |
* Perform [[static code analysis]] | * Perform [[static code analysis]] | ||
* Integrate projects with [https://code.google.com/p/address-sanitizer/ Address Sanitizer] | * Integrate projects with [https://code.google.com/p/address-sanitizer/ Address Sanitizer] | ||
| − | == Software testing == | + | === Software testing === |
* See things to test in [[QA TODO list]] | * See things to test in [[QA TODO list]] | ||
Revision as of 16:50, 6 June 2015
This article is a stub. You can help OpenVZ Wiki by expanding it. If you have ideas and suggestions on new features and improvements that you would like to see and help bring to OpenVZ, you can:
Write a specification - a short description what feature or improvement you would like to implement and why and how it should be implemented. Writing a good specification is an art, the finer points of which are discussed here. Once you have written your specification, you will need to discuss it with OpenVZ developers for inclusion in OpenVZ.
List below contains our current plans and TODO:
Per project
Per activity
Development
- Perform static code analysis
- Integrate projects with Address Sanitizer
Software testing
- See things to test in QA TODO list
- Add tests to Parallels Dispatcher code
DevOps
- Automate Virtuozzo Storage installation. Something like Ansible playbook for CEPH
- Automate CRIU development environment
- Automate CRIU code coverage measuring process
