From d292a3c5d016908d53587675bbe02c032a5a7a28 Mon Sep 17 00:00:00 2001
From: Steven Knight <knight@baldmt.com>
Date: Fri, 30 Jul 2004 22:32:56 +0000
Subject: Change the copyright statement to reflect ownership by the
 foundation.  Add and fix statements where needed.  Update scripts
 accordingly.

---
 HOWTO/README           | 19 +++++++++++++++++++
 HOWTO/change.txt       |  2 ++
 HOWTO/new-platform.txt |  2 ++
 HOWTO/new-script.txt   |  2 ++
 HOWTO/new-tool.txt     |  2 ++
 HOWTO/release.txt      |  5 +++++
 6 files changed, 32 insertions(+)

(limited to 'HOWTO')

diff --git a/HOWTO/README b/HOWTO/README
index cda76066..951c019f 100644
--- a/HOWTO/README
+++ b/HOWTO/README
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 Here you'll find plain text documentation of how to handle various SCons
 project procedures.  Files contained herein:
 
@@ -6,5 +8,22 @@ change.txt
         distributing aedist change sets, and updating the CVS repository
         on SourceForge.
 
+new-platform.txt
+        Steps to add a new Platform/*.py file.  This is probably out
+        of date.
+
+new-script.txt
+        Steps to add a new script or utility (like scons and sconsign)
+        to what we ship.
+
+new-tool.txt
+        Steps to add a new Tool/*.py file.  This is probably out of date.
+
 release.txt
 	Steps to go through when releasing a new version of SCons.
+
+subrelease.txt
+	Steps to go through when releasing a new subsidiary version
+	of SCons--for example, 0.95.1 after we've released 0.95.
+	So far, we've only done this to get some early testing on major
+	refactorings.
diff --git a/HOWTO/change.txt b/HOWTO/change.txt
index 049e8ebd..86e854d9 100644
--- a/HOWTO/change.txt
+++ b/HOWTO/change.txt
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 Handling a change set:
 
     --	Start the change:
diff --git a/HOWTO/new-platform.txt b/HOWTO/new-platform.txt
index 7e2fce8b..8aa11ec2 100644
--- a/HOWTO/new-platform.txt
+++ b/HOWTO/new-platform.txt
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 Adding a new Platform to the SCons distribution:
 
     --  Add the following files (aenf):
diff --git a/HOWTO/new-script.txt b/HOWTO/new-script.txt
index 8bb52228..f859c485 100644
--- a/HOWTO/new-script.txt
+++ b/HOWTO/new-script.txt
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 Steps for adding a new script/utility to the SCons packages.  Assume
 that you're creating a new man page, too.  In the template steps
 below, "newscript" is the name of the new script/utility being added.
diff --git a/HOWTO/new-tool.txt b/HOWTO/new-tool.txt
index c906b7fb..4297fe6e 100644
--- a/HOWTO/new-tool.txt
+++ b/HOWTO/new-tool.txt
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 Adding a new Tool to the SCons distribution:
 
     --  Add the following files (aenf):
diff --git a/HOWTO/release.txt b/HOWTO/release.txt
index 5b77b632..51dfb704 100644
--- a/HOWTO/release.txt
+++ b/HOWTO/release.txt
@@ -1,3 +1,5 @@
+__COPYRIGHT__
+
 This document covers how to prepare major releases of SCons--that is,
 releases numbered with X.Y format, such as 0.93, 1.0, etc.
 
@@ -91,6 +93,9 @@ Things to do to release a new X.Y version of SCons:
                 aecp rpm/scons.spec.in
                 vi rpm/scons.spec.in
 
+                aecp src/copyrightTests.py
+                vi src/copyrightTests.py
+
                 aecp src/setupTests.py
                 vi src/setupTests.py
 
-- 
cgit v1.2.1