Valgrind Home Information Source Code Documentation Contact How to Help Gallery
<< Q8: Other Architecures TOC  

Conclusion

This exercise was well worth doing. Please read my recommendations for specific things we should do to act on the results.

Actions taken directly as a result of survey

Website
- thoroughly overhauled
- more obvious URL (valgrind.kde.org)
- better structure -- menu, multiple pages
- better overview makes it clearer what Valgrind is, ie. it has multiple tools, etc
- added links to external tools, GUIs, CVS repository, etc
- bugzilla setup for bugs, feature requests
Skins
- started phasing out the term "skin", using "tool" instead; not using "skin" on website anymore
- eventually, there will be no default tool, so that users are forced to realise that Valgrind is more than just Memcheck. Users will be allowed to specify their own default tool in a .valgrindrc file.
Features
2.1.1 can run statically linked binaries.
Development
Bugzilla pages should ensure bug fixes and patches are not forgotten
Releases
we will always use proper version numbers from now on
Error Messages
small improvements made so far, will be seen in 2.1 series
Surveys
better version of survey written; information from responses should be much more focused, and directly applicable to understanding how Valgrind is used, and how to improve it.
<< Q8: Other Architecures TOC  


Bad, Bad Bug!

Copyright © 2000-2013 Valgrind™ Developers

Best Viewed With A(ny) Browser