From 908c1f6fc5f973353142370bd26603cebb2b7ad4 Mon Sep 17 00:00:00 2001 From: John Criswell Date: Mon, 21 Jul 2003 22:22:48 +0000 Subject: [PATCH] Updated from the discussion on July 21, 2003. Expanded upon testing priorities. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7225 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ReleaseTasks.html | 309 ++++++++++++++++++++++++----------------- 1 file changed, 185 insertions(+), 124 deletions(-) diff --git a/docs/ReleaseTasks.html b/docs/ReleaseTasks.html index d8f1ac4b194..5e8841a7f63 100644 --- a/docs/ReleaseTasks.html +++ b/docs/ReleaseTasks.html @@ -3,188 +3,249 @@ LLVM Public Release Project - - - + + +

LLVM Public Release Project

- - + +

What is this?
Priorities - +
What is this?
Priorities +
1. High Priority
2. Medimum Priority
3. Low Priority
4. High Priority
5. Medimum Priority
6. Low Priority
-

-
- - +
+ + - - - + - - - + + +

What is this?

- +

+ + 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. +

- + - - - + - - - + + +

Priorities

- +

+ The + list of things to do... +

- + - - - - + + - - - + + +

	+
	High Priority

- +

+ + +

Fix currently known bugs and write regression tests.

The gccld segfault from GlobalDCE.cpp.
The infinite loop for Tail Recursion.
The C++ constructor on dlopen() bug on Solaris.
+

Get autoconf to configure source and build directories according +to normal autoconf procedures.

Get test tree to work properly when configuring for a different +object root.
Get lex/yacc/etc output to be placed into the build tree, not the +source tree.
+

Test Suite

Create a nightly tester for Sparc.
Modify the test suite to have consistent output.
Add Pass/Fail tests to nightly tester.
+
Make the USE_SPEC option work for the test directory.
Cleanup test/Programs.

Document the procedure for extracting, building, and installing -LLVM.
Document how to start a project that uses LLVM and its build system.
+
Move the pool allocator and Reoptimizer code out of mainline CVS +and the release.
Documentation

Write documentation on the LLVM tools.
Review docs, ensuring that the information is up to date.

GCC C Front End
Ensure that the C front end compiles and installs nicely.
Place the C front end into the CVS repository.
-
Get the Reoptimizer code to work, ensuring that it does not -rely upon code outside of the source tree.
-
Create a system for managing development and releases +
- Create a fix (i.e. better hack) for the sys/select.h hack.
+
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.
Create a system for managing development and releases (i.e. CVS branching, labeling revisions, etc).
-

+ +

- + - - - - + + - - - + + +

	+
	Medium Priority

- +

Improve the testing framework.

Improve documentation on how to create an LLVM project.
+
Testing

Cleanup Reoptimizer tests so that they fit into the framework.
-
Create descriptions of what each test is doing (test specifications).
Cleanup Reoptimizer tests so that they fit into the framework.
+

Get the Reoptimizer tests to compile under x86.
-
Determine which sub-projects of LLVM will be distributed.
Create an installer for the software.
Move over to the autoconf method of specifying object code directories.
Add an install target in the Makefiles that will "install" LLVM, -easing deployment.
+
Create an installer for the software.
Put autoconf files into a separate directory (i.e. not llvm).

+ +

	+
	Low Priority

Make the projects/sample directory an actual example of LLVM -code.
Find and implement a bug reporting system (i.e. Bugzilla).
Test installations on various Linux distributions.
Create a license for the UIUC specific LLVM code.
Add a license file to the distribution.
Add a copyright notice and license information to each source - file.
Create man pages for the LLVM utilities.
-
GCC C Front End

Place the C front end into the CVS repository.
Ensure that the C front end compiles and installs nicely.
Add C++ support.
+

Release Management

Find and implement a bug reporting system (i.e. Bugzilla).

Make the projects/sample directory an actual example of LLVM code.
Testing

Create descriptions of what each test is doing (test specifications).
+
Test LLVM on various Linux distributions.
Test LLVM on various Solaris distributions.
Test LLVM on Solaris/x86.
+

Licenses

Create a license for the UIUC specific LLVM code.
Add a license file to the distribution.
Add a copyright notice and license information to each source +file.

Documentation

Create man pages for the LLVM utilities.
Create man pages for the LLVM libraries.
+

John Criswell

- -Last modified: Sat May 31 14:54:03 CDT 2003
-
-
+ + Last modified: Sat May 31 14:54:03 CDT 2003