summaryrefslogtreecommitdiff
path: root/HOWTO/README
diff options
context:
space:
mode:
authorSteven Knight <knight@baldmt.com>2004-07-30 22:32:56 +0000
committerSteven Knight <knight@baldmt.com>2004-07-30 22:32:56 +0000
commitd292a3c5d016908d53587675bbe02c032a5a7a28 (patch)
treef59b7025a29a357bed7170848520cc7575c5ab8b /HOWTO/README
parentcd46401690172d1b2d2b9cc3a78379f9af041e85 (diff)
downloadscons-d292a3c5d016908d53587675bbe02c032a5a7a28.tar.gz
Change the copyright statement to reflect ownership by the foundation. Add and fix statements where needed. Update scripts accordingly.
Diffstat (limited to 'HOWTO/README')
-rw-r--r--HOWTO/README19
1 files changed, 19 insertions, 0 deletions
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.