LLVM Public Release Project
This document is a list of things to do before the LLVM project is
publicly released. It will provide a checklist so that we know
what has been done and what is left to be done. It will also keep
a "wishlist" of desirable features.
The
list of things to do...
- Test Suite
- Finish QMTest Integration.
- Documentation
- Write documentation on the LLVM tools.
- Create release notes.
- Expand documentation on creating an LLVM project.
- Create a FAQ for common problems.
- Review docs, ensuring that the information is up to date.
- Add an install doc to the source tree (web version gets
updated in main branch).
- Improve GCC C/C++ Front End
- Licenses
- Ensure all software in source tree has proper license.
- Check licenses in test/Programs to ensure everything is good.
- Create license files for anything in the distribution that is
not under our license.
- Ensure SafeCode builds.
- Ensure SPEC works.
- Create a system for managing development and releases (i.e. CVS
branching, labeling revisions, etc).
- Move utils/Burg, utils/Tblgen, and lib/Support into support/lib
and support/tools directory.
- Improve documentation on how to create an LLVM project.
- Test Suite
- Add Feature and Regression tests to nightly tester.
- Develop better QMTest database method.
- Write regression tests.
- The C++ constructor on dlopen() bug on Solaris.
- Find and implement a bug reporting system (i.e. Bugzilla).
- GCC C Front End
- Place the C front end into the CVS repository.
- Ensure that the C front end compiles and installs nicely.
- Create an installer for the software.
- Testing
- Create descriptions of what each test is doing (test
specifications).
- Test LLVM on various Linux distributions.
- Test LLVM on various Solaris versions.
- Test LLVM on Solaris/x86.
- Documentation
- Create man pages for the LLVM utilities.
- Create man pages for the LLVM libraries.
- Rewrite this page without Netscape Composer :)
John Criswell
Last
modified: Sat May 31 14:54:03 CDT 2003