<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to you under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->

1. A large number of the scripts expect builds and UpdateInfo to exist in ${DERBYDIR}/testing/. 
   A better location is ${DERBYDIR}/. 
   Fix the relevant scripts to use ${DERBYDIR}/builds and ${DERBYDIR}/UpdateInfo.
   (Currently handled using symlinks....)

2. Merge production of Full and Limited reports. No need to have Limited at all?

3. "Exception handling" in the scripts should be better....

4. Convert the scripts to Ant! (and Java...)

5. Use some standardized mechanism to format the report pages: E.g. XSLT, XPATH...

6. Keep revision, build and test data in a (Derby) database.
