From df92a34720a8511f63a12abcd7e0ca2deeeca4d1 Mon Sep 17 00:00:00 2001 From: William Deegan Date: Mon, 30 Apr 2018 10:11:01 -0400 Subject: remove obsolete directory www. Was leftover from when SVN was hosted on tigris.org. This directory affected some project pages on tigris.org --- www/bug-submission.html | 234 -------------- .../Administrivia/snippets/HtmlSnippet1.html | 1 - .../Administrivia/snippets/description.txt | 1 - .../Administrivia/snippets/page.xml | 10 - www/cn-project-pages/snippets/page.xml | 16 - www/cn-project-pages/structure.xml | 10 - www/favicon.ico | Bin 1406 -> 0 bytes www/feature-request.html | 99 ------ www/gen_sched_table.py | 51 --- www/index.html | 288 ----------------- www/patch-submission.html | 355 --------------------- www/project_highlights.html | 24 -- www/project_issues.html | 123 ------- www/project_tools.html | 41 --- www/roadmap.html | 173 ---------- www/schedule | 19 -- 16 files changed, 1445 deletions(-) delete mode 100644 www/bug-submission.html delete mode 100644 www/cn-project-pages/Administrivia/snippets/HtmlSnippet1.html delete mode 100644 www/cn-project-pages/Administrivia/snippets/description.txt delete mode 100644 www/cn-project-pages/Administrivia/snippets/page.xml delete mode 100644 www/cn-project-pages/snippets/page.xml delete mode 100644 www/cn-project-pages/structure.xml delete mode 100644 www/favicon.ico delete mode 100644 www/feature-request.html delete mode 100755 www/gen_sched_table.py delete mode 100644 www/index.html delete mode 100644 www/patch-submission.html delete mode 100644 www/project_highlights.html delete mode 100644 www/project_issues.html delete mode 100644 www/project_tools.html delete mode 100644 www/roadmap.html delete mode 100644 www/schedule diff --git a/www/bug-submission.html b/www/bug-submission.html deleted file mode 100644 index abc855b..0000000 --- a/www/bug-submission.html +++ /dev/null @@ -1,234 +0,0 @@ - - -Bug Submission - - - -
-

scons
Bug Submission

- -

-You must now -log in -to a tigris.org account -before submitting a new bug report! -

- -

-Bugs should be reported at the -"Enter Issue" page. -Please follow the submission guidelines below -to make sure your bug report contains the necessary information. -A more detailed set of submission steps -can be found below. -

- -

-The above URL is set up for reporting a bug in SCons itself. -If you are reporting a problem in some other aspect of the SCons Project -(such as the documentation, or any of the web pages), -you must change the Subcomponent field of the submission form -to some other appropriate value. -

- -
- -
- -

Guidelines for a Useful Bug Report

- -

-Your bug will be much more likely to get diagnosed and fixed -if you supply all the necessary information to make it easy to do so. -

- - - -

Steps for Submitting a Bug Report

- -

-The following guides you step-by-step through the -process of submitting a new SCons bug report. -

- -

-NOTE: Creating a bug report with an attached file or files -(such as a .tar.gz or .zip file containing a sample configuration) -is a two-step process in the tigris.org Issue Tracker. -You must first create the bug report, -and then attach the file(s) in a separate step, -as described below. -

- - - -
- - - diff --git a/www/cn-project-pages/Administrivia/snippets/HtmlSnippet1.html b/www/cn-project-pages/Administrivia/snippets/HtmlSnippet1.html deleted file mode 100644 index a311062..0000000 --- a/www/cn-project-pages/Administrivia/snippets/HtmlSnippet1.html +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/www/cn-project-pages/Administrivia/snippets/description.txt b/www/cn-project-pages/Administrivia/snippets/description.txt deleted file mode 100644 index 08c477b..0000000 --- a/www/cn-project-pages/Administrivia/snippets/description.txt +++ /dev/null @@ -1 +0,0 @@ -Administrative information and links \ No newline at end of file diff --git a/www/cn-project-pages/Administrivia/snippets/page.xml b/www/cn-project-pages/Administrivia/snippets/page.xml deleted file mode 100644 index 7086b8d..0000000 --- a/www/cn-project-pages/Administrivia/snippets/page.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - - Administrative links - HtmlSnippet1.html - - - - diff --git a/www/cn-project-pages/snippets/page.xml b/www/cn-project-pages/snippets/page.xml deleted file mode 100644 index 005b144..0000000 --- a/www/cn-project-pages/snippets/page.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - - </component> - <component visibility="1" type="Html" order="2"> - <title localize="false" /> - <filename>index.html</filename> - </component> - <component visibility="1" type="Subproject" order="3"> - <title localize="true">Subprojects - - - - diff --git a/www/cn-project-pages/structure.xml b/www/cn-project-pages/structure.xml deleted file mode 100644 index 2c1f3bb..0000000 --- a/www/cn-project-pages/structure.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - - g2uyOi - Administrivia - Administrivia - 1 - - - diff --git a/www/favicon.ico b/www/favicon.ico deleted file mode 100644 index 1541e5b..0000000 Binary files a/www/favicon.ico and /dev/null differ diff --git a/www/feature-request.html b/www/feature-request.html deleted file mode 100644 index e644a16..0000000 --- a/www/feature-request.html +++ /dev/null @@ -1,99 +0,0 @@ - - -Feature Requests - - - -
-

scons
Feature Requests

-
- -

-You must now -log in -to a tigris.org account -before submitting a feature request! -

- -

-Feature requests should be submitted to the -"Enter Issue" page. -A more detailed set of submission steps -can be found below. -

- -

-The "Enter Issue" links on this page, -by default, create a FEATURE request, -a request for completely new SCons functionality. -If your request is for modified behavior -of an already-existing SCons feature, -you may wish to change the Issue type -to an ENHANCEMENT request. -If you're not sure, leave the issue as a FEATURE request; -it can be reclassified in the future, if necessary. - - -

- -

Steps for Submitting a Feature Request

- -

-The following guides you step-by-step through the -process of submitting a feature request. -

- - - -
- - - diff --git a/www/gen_sched_table.py b/www/gen_sched_table.py deleted file mode 100755 index 85b1b81..0000000 --- a/www/gen_sched_table.py +++ /dev/null @@ -1,51 +0,0 @@ -#!/usr/bin/env python -from __future__ import print_function - -import sys -import datetime - -months = ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', - 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'] - -print('') -def row(*cells, **kw): - td = kw.get('tr','td') - print(' ') - for cell in cells: - print(' <%s>%s' % (td,cell,td)) - print(' ') -row('Estimated date', 'Type', 'Comments', tr = 'th') - -if len(sys.argv) > 1: - f = open(sys.argv[1]) -else: f = open('schedule') -now = None -current = 'UNKNOWN' -for line in f: - if line[0] == '#': continue # comment - if line[0] == '=': - date,current = line[1:].strip().split(None, 1) - now = datetime.date(*tuple([int(i) for i in date.split('-')])) - continue - if line[0] == '+': - incr,type,desc = line[1:].strip().split(None,2) - now = now + datetime.timedelta(int(incr)) - else: - print('dunna understand code', line[0]) - sys.exit(1) - #name = current + '.d' + str(now).replace('-','') - date = '%s-%s-%s' % (now.day,months[now.month-1],now.year) - if type == 'ck': - category = 'Ckpt' - elif type == 'rc': - category = 'RC' - else: - category = current = type - row(date, category, desc) -print('
') - -# Local Variables: -# tab-width:4 -# indent-tabs-mode:nil -# End: -# vim: set expandtab tabstop=4 shiftwidth=4: diff --git a/www/index.html b/www/index.html deleted file mode 100644 index 203435d..0000000 --- a/www/index.html +++ /dev/null @@ -1,288 +0,0 @@ - - - - - -
- -

What is SCons?

- -

SCons is a next-generation, -cross-platform, build tool. -Think of SCons as an improved -substitute for the classic -Make utility -with integrated functionality -similar to autoconf/automake -and compiler caches such as ccache. -

- -

-Unlike build tools that invent their own mini-language -or wedge a scripting language onto some other -configuration file syntax, -SCons configuration files -are actually Python scripts. -The ability to script your build -gives you a tremendous amount of flexibility -to solve complicated build problems -in surprisingly small amounts of maintainable code. -

- -

-In short, SCons is an easier, more reliable -and more flexible way to build software. -

- - - -

SCons Features

- - - - - -

Future

- -See the Roadmap page. - -
- - - diff --git a/www/patch-submission.html b/www/patch-submission.html deleted file mode 100644 index a2d9b95..0000000 --- a/www/patch-submission.html +++ /dev/null @@ -1,355 +0,0 @@ - - -Patch Submission - - - -
-

scons
Patch Submission

-
- -

-You must now -log in -to a tigris.org account -before submitting a patch! -

- -

-Patches should be submitted to the -"Enter Issue" page. -Please follow the submission guidelines below -to make sure your patch contains the necessary information. -A more detailed set of submission steps -can be found below. -

- - - -
- -

Guidelines for Patch Submission

- -

-To try to maintain and improve the quality of SCons releases, -we have some pretty high standards for the quality of patches -that make it into the SCons code base. -This list of guidelines describes how to make it as -easy as possible for your patch to be accepted for integration. -We're still interested in your code -even if you don't follow all of these guidelines, -but then your patch will more than likely sit in the queue -until someone else has time to supply all of the -necessary missing items. -

- - - -

Steps for Submitting a Patch

- -

-The following guides you step-by-step through the -process of submitting a patch to SCons. -

- -

-NOTE: Attaching a file or files -(such as a .tar.gz or .zip file containing your patch) -is a two-step process in the tigris.org Issue Tracker. -You must first create the patch issue in the Tracker, -and then attach the file(s) in a separate step, -as described below. -

- - - -
- - - diff --git a/www/project_highlights.html b/www/project_highlights.html deleted file mode 100644 index 98f00bc..0000000 --- a/www/project_highlights.html +++ /dev/null @@ -1,24 +0,0 @@ - - - - - - -

-09 Sep 2011: -Release 2.1.0 is now available at the -download page. -

- - -

-15 Aug 2010: -Release 2.0.1 is now available at the -download page. -

- - - - - - diff --git a/www/project_issues.html b/www/project_issues.html deleted file mode 100644 index dc28ca8..0000000 --- a/www/project_issues.html +++ /dev/null @@ -1,123 +0,0 @@ -
-

scons
Issue Tracker -

-
- - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Query database - Search for issues and defects here or find a specific issue. Always search first before reporting an issue to avoid duplication. -
-

- Issue # - -

-
-

- Common queries: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All Open Issues
  • Bug Reports:
All Open Non-Open
  • Enhancement:
All Open Non-Open
  • Feature Requests:
All Open Non-Open
  • Patches:
All Open Non-Open
  • Tasks:
All Open Non-Open
-
Enter an issue - - To enter an issue, you must first be a project member and know the component you want to report on. - - - -

- -Enter: -

- -
My issues - View both active issues assigned to you and those that you have entered. -
My preferences - View and edit your Issue Tracker user settings. -
Reports - Generate and view issue tracking reports. -
Configuration options - - Add, view and edit Issue Tracker configuration parameters, including project member permissions, issue tracking groups, project components and subcomponents, etc. -
-
diff --git a/www/project_tools.html b/www/project_tools.html deleted file mode 100644 index cf80234..0000000 --- a/www/project_tools.html +++ /dev/null @@ -1,41 +0,0 @@ - -
  • SCons Home Page
    • -
  • SCons Wiki
    • - - -
    -
  • Project Membership
    • -
  • Announcements
    • -
  • Discussion lists/fora
    • - -
  • Documents & files
    • -
  • Browse source code
    • -
  • Project metrics
    • -
    - -
    -
  • - -Issue Tracker - -
    • -
    - -
    -
  • Roadmap
    • diff --git a/www/roadmap.html b/www/roadmap.html deleted file mode 100644 index 333d0fd..0000000 --- a/www/roadmap.html +++ /dev/null @@ -1,173 +0,0 @@ - - -scons: Release Roadmap - - - -
    -

    Release Roadmap

    -
    - -
    - -

    Current Releases

    - -

    -The current stable release is 2.1.0, released 09 Sep 2011. -The latest 2.1.x release is 2.1.0, released 09 Sep 2011. -

    - -

    -The latest 1.3.x release is 1.3.1, released 25 July 2010. -

    - -

    Upcoming Releases

    - -

    -Our goal is to meet the dates -for release candidates and the releases themselves; -the beta checkpoint dates are our best guess as this was published, -but they may be adjusted without notice. -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Estimated dateTypeComments
    May 2010CkptBeta for 2.0; breaks backward compatibility
    June 2010RCRelease candidate for 2.0.
    June 20102.0Public release that breaks backward compatibility and drops deprecated features
    July 2010CkptBeta for testing new features.
    Aug 2010CkptBeta for testing new features.
    Sept 2010RCRelease candidate for 2.1.
    Oct 20102.1First minor release of v2
    - - - -

    Release Planning

    - -

    Release numbering

    - -

    -Our release numbers are of the form major.minor.revision. -

    - -
      -
    • -Major release (1.0, 2.0, 3.0, etc.) -

      -The major number increments when one of two things happens: -

      -
        -
      • The release knowingly breaks backwards compatibility in some way. -
      • The release knowingly causes a rebuild when you upgrade. -
      -

      -Our goal is that as a user of SCons, -you should always be able to upgrade to a later -release of the same major version -with complete confidence that your build will not break. -We expect that our major releases will be long-lived platforms -with many minor releases to add functionality and fix bugs. -

      -
      • -
    • -Minor release (1.1, 1.2, 1.3, etc.) -

      -Minor numbers increment for releases -that add new functionality and/or bug fixes -to an existing major release. -Any new functionality will never knowingly break backwards compatibility -with any previous minor releases from the same major release. -

      -
      • -
    • -Bug-fix revisions (1.0.1, 1.1.1, 1.2.1, etc.) -

      -Revision numbers are appended and/or incremented -whenever a critical bug fix is necessary -for a major or minor release. -Because most new functionality and bug fixes -will be delivered in minor releases, -we expect that there will be few of these—at most -one per minor release. -

      -
      • -
    • -Release candidates (x.y.z.dyyyymmdd) -

      -A release candidates is a special form of checkpoint -(see below) -that is expected to be the next major or minor release. -If blocking issues show up in the candidate, -another candidate will normally be issued -(potentially delaying the release date), -otherwise the candidate will be repackaged as the major or minor release. -

      -
      • -
    • -Checkpoints (x.y.z.dyyyymmdd) -

      -A checkpoint has a 'dyyymmdd' suffix -and is made every couple of weeks between major or minor releases. -It is intended for beta testing new features -and for ensuring that bug fixes work as intended. -Although existing features from the previous release will not change, -compatibility of features under test is not guaranteed between checkpoints -(i.e., the implementation of the feature may change). -Checkpoints are intended not only to allow for wider testing, -but also to make new features available to users -(who may urgently need one of them) -in advance of them being published in the next major or minor release. -

      -
      • -
    - -
    - - - diff --git a/www/schedule b/www/schedule deleted file mode 100644 index 4b1e9eb..0000000 --- a/www/schedule +++ /dev/null @@ -1,19 +0,0 @@ -#=2008-09-13 1.0.1 -#=2008-10-01 Release candidate for 1.1. -#=2008-10-10 1.1.0 -=2008-12-01 1.1.0 -+4 rc Release candidate for 1.2. (released 7-Dec) -+7 1.2 Second minor release of 1.0. (released 21-Dec) -+17 ck Beta for testing new features. -+14 ck Beta for testing new features. -+7 rc Release candidate for 1.3. -+7 1.3 Third minor release of 1.0. -+7 ck Beta for 2.0; breaks backward compatibility -#+7 ck Beta for 2.0. -+7 rc Release candidate for 2.0. -+7 rc Release candidate for 2.0, if needed. -+7 2.0 Public release that breaks backward compatibility and drops deprecated features -+21 ck Beta for testing new features. -+21 ck Beta for testing new features. -+21 rc Release candidate for 2.1. -+7 2.1 First minor release of 2.0 -- cgit v0.12