[llvm-commits] CVS: llvm-www/SVNMigration.html

Reid Spencer reid at x10sys.com
Tue Jun 26 13:46:19 PDT 2007

Changes in directory llvm-www:

SVNMigration.html updated: 1.15 -> 1.16
Log message:

Update with current information.

Diffs of the changes:  (+96 -31)

 SVNMigration.html |  127 ++++++++++++++++++++++++++++++++++++++++--------------
 1 files changed, 96 insertions(+), 31 deletions(-)

Index: llvm-www/SVNMigration.html
diff -u llvm-www/SVNMigration.html:1.15 llvm-www/SVNMigration.html:1.16
--- llvm-www/SVNMigration.html:1.15	Fri Jun 15 15:03:47 2007
+++ llvm-www/SVNMigration.html	Tue Jun 26 15:45:56 2007
@@ -4,23 +4,33 @@
 <div class="www_text">
   <p>This document contains notes about the planned migration of the CVS code
   repository to Subversion.</p>
+  <li><a href="#schedule">Schedule</a></li>
+  <li><a href="#impact">Impact</a>
+  <li><a href="#status">Status</a>
+  <li><a href="#renaming">Module Renaming</a>
+  <li><a href="#branches">Branch Status</a>
+  <li><a href="#tags">Tag Status</a>
+  <li><a href="#process">Migration Process</a>
-<div class="www_subsection">Schedule</div>
+<div class="www_subsection"><a href="schedule">Schedule</a></div>
 <div class="www_text">
-  <p><b>When</b>: (Tentatively) June 25, 2007, approx. 1pm CDT (Central Time USA) or 18:00 GMT).</p>
-  <p><b>Duration</b>: 4 hours</p>
-  <p><b>Notices:</b>: Notices will be sent out 1 week before, 1 day before, and
+  <p><b>When</b>: June 29, 2007, 09:00 CDT, 07:00 PDT, 14:00 UTC.</p>
+  <p><b>Duration</b>: Approximately 4 hours</p>
+  <p><b>Notices:</b>: Notices will be sent out 3 days before, 1 day before, and
   1 hour before the conversion actually takes place.</p>
-  <p><b>Impact</b>: Both CVS and Subversion will be unavailable for approximately 
-  4 hours while the migration takes place. Once completed, CVS will be restored
-  in read-only mode and Subversion will permit read-write access.</p>
+  <p><b>Impact</b>: CVS commits will be unavailable for approximately 4 hours
+  while the migration takes place. Anonymous CVS checkout will still be allowed
+  during this time frame. Once the migration is done, CVS will remain in
+  read-only mode and Subversion will be enable for read and write access.</p>
   <p><b>Fallback Plan</b>: If the conversion cannot be completed successfully
   in 4 hours, we will turn CVS commit access back on and try the migration
   again at a later date.</p>
-<div class="www_subsection">User Impact</div>
+<div class="www_subsection"><a href="impact">User Impact</a></div>
 <div class="www_text">
   <p>Here are some things you need to know about how to use Subversion once the
   migration is done and how to prepare for the change.</p>
@@ -28,32 +38,42 @@
     <li><b>Subversion Version</b>: 1.4.3. You can use older clients, but we
     recommend that you upgrade to 1.4.3 to gain most benefit.</li>
     <li><b>URLS</b>: Subversion uses URLs to specify the repository. Our 
-    configuration uses HTTP URLs. The host name portion of the URL for all
-    LLVM related repositories is svn.llvm.org (which redirects to 
-    subversion.cs.uiuc.edu). We encourage you to use the svn.llvm.org host name
-    because that one will be correct in perpetuity as the redirect might not be.
-    <li><b>Repository Access</b>: There are two ways to access the
-    repository: public (anonymous, read-only access) and private (named, 
-    read-write access).</li>
-    <li><b>Public Access</b>: The URL for the public access repository is
-    <a href="http://svn.llvm.org/pub/svn/llvm">http://svn.llvm.org/pub/svn/llvm</a>
-    Use this URL with the <tt>svn checkout</tt> command to obtain a read-only
-    copy of LLVM without a username or password.</li>
-    <li><b>Private Access</b>: The URL for the private access repository is
-    <a href="https://svn.llvm.org/svn/llvm">http://vn.llvm.org/svn/llvm</a>. 
-    Use this URL with the <tt>svn checkout</tt> command to obtain read-write
-    access to the LLVM repository. The <tt>svn</tt> command will prompt you for
-    your user name and password.</li>
-    <li><b>Browsable URLs</b>: Both the public and private access URLs are
-    browsable with any web browser.</li>
+    configuration uses HTTPS URLs. The host name portion of the URL for all
+    LLVM related repositories is <tt>llvm.org</tt>. The URL for accessing any of
+    the modules in the LLVM repository is:
+    <a href="https://llvm.org/svn/llvm-project">
+      https://llvm.org/svn/llvm-project</a>. Note that the URL uses the HTTPS
+    protocol. This is necessary to ensure that passwords are not transmitted in
+    the clear.</li>
+    <li><b>Browsing</b>: You can browse the latest revision of the repository
+    with any web browser by just pointing it at the URL shown above.</li>
+    <li><b>Modules</b>: The repository contains several modules. Each module is
+    contained in a top level directory and has its own <tt>trunk</tt>,
+    <tt>branches</tt>, and <tt>tags</tt> directories at the second level. Some
+    of the modules have changed name. See the <a href="#renaming">Renaming</a>
+    section for details.</li>
+    <li><b>Checkout Access</b>: You can checkout any llvm module by simply using
+    the svn command with the above URL. For example:<pre>
+    svn co https://llvm.org/svn/llvm-project/llvm/trunk llvm
+    </pre>This will give you a local <tt>llvm</tt> directory that contains the
+    contents of the "llvm" module.</li>
+    <li><b>Commit Access</b>: If you have commit access you will need to supply
+    a user name and password to commit. We recommend that you check out using a
+    URL like this: <tt>https://uname@llvm.org/svn/llvm-project/...</tt>. You 
+    should replace "uname" with your actual user name.  When you attempt to 
+    commit you will get a password prompt from the Subversion command. Enter 
+    your password to complete the commit.</li>
     <li><b>Available Now:</b>: You can try these out now. Only a few users have
     commit access (those who are testing it). Any changes made will be discarded
-    before the June 5th conversion.</li>
+    before the June 29th conversion.</li>
-<div class="www_subsection">Notes</div>
+<div class="www_subsection"><a href="status">Status</a></div>
 <div class="www_text">
+  <p><b>Status as of 2007-06-26</b><br/>We are finally ready to do the migration
+  on June 29th. Access to the final repository location is now available. It
+  will be updated twice per day until the conversion occurs.</p>
   <p><b>Status as of 2007-04-20</b><br/>We have successfully migrated all the
   sub-projects targeted for conversion over the UIUC internal network. The
   Subversion snapshot is available for access (for testing only).</p>
@@ -80,7 +100,7 @@
 <!-- *********************************************************************** -->
-<div class="www_subsection"><a name="branches">Renaming</a></div>
+<div class="www_subsection"><a name="renaming">Renaming</a></div>
 <div class="www_text">
   <p>Since everything will be in one SVN repository, we thought we'd take this
   opportunity to rename some top level directories to reduce redundancy. This
@@ -99,7 +119,7 @@
   <p><b>NOTE</b>: Due to synchronization of commits in the conversion process, 
-  we will likely transition all of the above to Subversion in one shot. 
+  we will transition all of the above to Subversion in one shot. 
   This will allow SVN revision numbers to increase temporally instead 
   of disjointedly if the projects were imported one at a time. It also 
   permits revision groups to span across projects. For example, 
@@ -212,6 +232,51 @@
+<!-- *********************************************************************** -->
+<div class="www_subsection"><a name="process">Migration Process</a></div>
+<div class="www_text">
+  <p>The following describes the sequence of events that need to occur in order
+  to complete the migration from CVS to Subversion. While this is mostly
+  internal to the people doing the conversion, it may be useful for you to see
+  what the process is.</p>
+  <p>The list below shows the logical order in which things need to be done
+  without assigning any dates to them.</p>
+  <ol>
+    <li><b>(done) Test Repository Up</b>. </li>
+    <li><b>Integrate email notification script</b>. The email notification
+    script needs to be put into the convert script so that conversion
+    automatically has the post-commit hook set up.</li>
+    <li><b>Configure ViewVC</b>. We need to get ViewVC up and running so that it
+    is presenting the SVN repository from its new host (Zion). The main web 
+    page probably needs to be updated too.</li>
+    <li><b>(done) NewNightlyTest.pl -usesvn</b>. This script needs to be updated
+    so that the -usesvn option gets the right repository by default.</li>
+    <li><b>Final CutOver</b>. The cut-over to SVN needs to be done. Currently
+    scheduled for 6/29/2007 at 9:00am CDT.</li>
+    <li><b>NewNightlyTest.pl Defaults to SVN</b>. This script needs to be 
+    updated so that the default repository is Subversion and the ability to 
+    use CVS is taken away.</li>
+    <li><b>Documents</b>. We need to rewrite the /docs/ url to go to
+    /svn/llvm-project/llvm/trunk/docs/. There's no need to have an auto-update
+    rule any more as this will always provide the latest.</li>
+    <li><b>llvm-www</b>. The web pages (but not releases sibudir) for the main 
+    web site need to be put into a new "website" module in Subversion. We can 
+    do this with the cvs2svn script again and (I think) tell it to ignore the 
+    releases directory.</li>
+    <li><b>Web Site Auto Update</b>. We don't need to check out any more, we
+    just need a rewrite rule. Basically, http://llvm.org/ needs to be rewritten
+    as accessing http://llvm.org/svn/llvm-project/website/trunk/. This is sure
+    to provde the latest version without a check out.</li>
+    <li><b>Releases</b>. We need a strategy for dealing with releases. I'd be
+    fine if these were just put in the web server's document root and not
+    version controlled. They are huge and not changed much (ever). In any event,
+    whatever we do we should jsut rewrite the /releases/ URL to point to some
+    place where the releases are stored (or create /releases/ in the document
+    root).</li>
+  </ol>
 <!-- *********************************************************************** -->
@@ -219,6 +284,6 @@
   src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
   <a href="http://validator.w3.org/check/referer"><img
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
-<br/>Last modified: $Date: 2007/06/15 20:03:47 $
+<br/>Last modified: $Date: 2007/06/26 20:45:56 $
 <!--#include virtual="footer.incl" -->

More information about the llvm-commits mailing list