diff options
| author | William Deegan <bill@baddogconsulting.com> | 2015-09-21 17:03:12 (GMT) |
|---|---|---|
| committer | William Deegan <bill@baddogconsulting.com> | 2015-09-21 17:03:12 (GMT) |
| commit | 0941093e0e5a030faa49968457638a3a6aee7ad8 (patch) | |
| tree | 6d33513c14eb6eac0531dd050de0ecca4c39bd79 /HOWTO/README | |
| download | SCons-2.4.0.zip SCons-2.4.0.tar.gz SCons-2.4.0.tar.bz2 | |
release 2.4.02.4.0
Diffstat (limited to 'HOWTO/README')
| -rw-r--r-- | HOWTO/README | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/HOWTO/README b/HOWTO/README new file mode 100644 index 0000000..951c019 --- /dev/null +++ b/HOWTO/README @@ -0,0 +1,29 @@ +__COPYRIGHT__ + +Here you'll find plain text documentation of how to handle various SCons +project procedures. Files contained herein: + +change.txt + How changes are integrated, including generating and + 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. |
