1. SCons
  2. web
  3. scons-website

Commits

Gary Oberbrunner  committed fdfbce0

Updated dev pages from discussing Subversion to Mercurial

  • Participants
  • Parent commits c6565eb
  • Branches default

Comments (0)

Files changed (2)

File dev.php

View file
 class="sconslogo">SCons</span>.
 Lines of test code currently outnumber lines of code in SCons itself
 by more than 2.5 to one.
-<li>We used the Aegis change management system to control the development and
-testing process in the past.
-<li>Now you can use Subversion as a front end for submitting patches.
+<li>You can use Mercurial (via Bitbucket) as a front end for submitting patches.
 </ul>
 
 </p>
 The <span class="sconslogo">SCons</span> project page at
 <a href="http://www.tigris.org">Tigris.org</a>.
 This is the center of active SCons development,
-hosting the main source code repository
-and issue tracker (bugs, patches, tasks, etc.).
+hosting the issue tracker (bugs, patches, tasks, etc.).
+The old Subversion repository is there, but we now use
+<a href="https://bitbucket.org/scons/scons">Bitbucket</a>
+to host the official source repository.
 </div>
 </div>
 
 
 <div class="link">
 <div class="linkname">
-<a href="http://scons.tigris.org/source/browse/scons/">Subversion&nbsp;repository</a>
+<a href="https://bitbucket.org/scons/scons">Bitbucket&nbsp;repository</a>
 </div>
 <div class="linkdesc">
 Our
-<a href="http://scons.tigris.org/source/browse/scons/">browsable Subversion repository</a>
-is kept at <a href="http://www.tigris.org">Tigris.org</a>.
-The <tt>trunk/</tt> contains the most-current development,
-while <tt>checkpoint/</tt> and <tt>release/</tt> contain
-the most-recent beta release and the most-recent public release, respectively.
-Most long-term development is carried out on subsidiary <tt>branches/</tt>.
-To get the sources, see the
-<a href="http://scons.tigris.org/servlets/ProjectSource">download
-instructions</a>.
+<a href="https://bitbucket.org/scons/scons">browsable Bitbucket repository</a>
+is kept at <a href="http://www.bitbucket.org">Bitbucket.org</a>.
+The <tt>default/</tt> branch contains the most-current development,
+but some long-term development is carried out on subsidiary <tt>branches/</tt>.
+Anyone may clone the main repository from bitbucket.
 See the <a href="http://scons.org/wiki/BranchAndMerge">Branching and Merging</a>
 page in our wiki for a description of the different branches
 and how we handle branch management.

File guidelines.php

View file
 control system(s):
   <ol class="decimal">
   <li>
-  The main source tree is kept in Subversion at tigris.org.
+  The main source tree is kept in Mercurial at <a href="https://bitbucket.org/scons/scons">Bitbucket</a>.
   </li>
   <li>
-  CVS archive of the source tree is still available at SourceForge.
-  </li>
-  <li>
-  SK is still using the Aegis change management system
-  for his back-end development process, primarily for its
-  management of tests.  The SCons packaging is still
-  written assuming an Aegis infrastructure, but will change
-  to Subversion-based packaging at some point.
+  SVN archive of the source tree is still available at Tigris.
   </li>
   </ol>
 <li>
 
 
 <li>
-Using Subversion for SCons development
+Using Mercurial for SCons development
 <p>
 <ol class="decimal">
 <li>
-Developers using Subversion may, but need not,
-be registered as Tigris.org or SourceForge developers.
-</li>
-<li>
-Developers using Subversion should submit
-patches following the normal
-<a href="http://scons.tigris.org/patch-submission.html">patch submission</a>
-guidelines.
+Developers using Mercurial may, but need not,
+be registered at Bitbucket.org, and should submit pull
+requests to <a> href="https://bitbucket.org/scons/scons">
+the SCons Bitbucket account</a>.
 </li>
 </ol>
 </p>
 Integration
 <p>
 <ol class="decimal">
-<li>
-The main line of SCons integration is still under the control of the
-Aegis change management system, as administered by SK on his system.
-We want move to Subversion-based integration and packaging.
-</li>
-<li>
-Changes to SK's main Aegis repository get propagated
-automatically to the Tigris.org and SourceForge CVS repositories.
-</li>
 </ol>
 </p>
 </li>