incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r654638 - in /incubator/public/trunk: site-author/guides/mentor.xml site-publish/guides/mentor.html
Date Thu, 08 May 2008 21:49:00 GMT
Author: rdonkin
Date: Thu May  8 14:48:56 2008
New Revision: 654638

URL: http://svn.apache.org/viewvc?rev=654638&view=rev
Log:
More information about imports

Modified:
    incubator/public/trunk/site-author/guides/mentor.xml
    incubator/public/trunk/site-publish/guides/mentor.html

Modified: incubator/public/trunk/site-author/guides/mentor.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/mentor.xml?rev=654638&r1=654637&r2=654638&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/mentor.xml (original)
+++ incubator/public/trunk/site-author/guides/mentor.xml Thu May  8 14:48:56 2008
@@ -266,6 +266,21 @@
         A public record MUST be made of the code imported. If the import is not
         attached to JIRA then it MUST be committed to version control.
         </p>
+        <section id='svn-history'><title>Importing History</title>
+          <p>
+The incoming code can either be committed as a snapshot or as a complete version
+control export including history (provided that the import is available in a format
+readable by subversion). 
+Importing with history allows existing open source projects who want to maintain 
+older versions at Apache to easily perform source diffs and so on. Import just the 
+latest code allows a clean break to be made with the past. The choice is left to 
+the community of the incoming project.
+          </p><p>
+The infrastructure team will perform the import including
+mapping IDs but it is an operation that requires skill, time and care. In this case, 
+please ask the infrastructure team politely.
+          </p>
+        </section>
       </section>
       <section id='crypto-audit'><title>Audit Cryptography</title>
         <p>

Modified: incubator/public/trunk/site-publish/guides/mentor.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/mentor.html?rev=654638&r1=654637&r2=654638&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/mentor.html (original)
+++ incubator/public/trunk/site-publish/guides/mentor.html Thu May  8 14:48:56 2008
@@ -181,6 +181,12 @@
 <li><a href='#initial-import-code-dump'>
 Initial Code Dump
  </a>
+ <ul>
+<li><a href='#svn-history'>
+Importing History
+ </a>
+</li>
+</ul>
 </li>
 <li><a href='#crypto-audit'>
 Audit Cryptography
@@ -538,6 +544,25 @@
         A public record MUST be made of the code imported. If the import is not
         attached to JIRA then it MUST be committed to version control.
         </p>
+<h5> 
+   <a name="svn-history">Importing History</a> 
+</h5> 
+<div class="section-content">
+<p>
+The incoming code can either be committed as a snapshot or as a complete version
+control export including history (provided that the import is available in a format
+readable by subversion). 
+Importing with history allows existing open source projects who want to maintain 
+older versions at Apache to easily perform source diffs and so on. Import just the 
+latest code allows a clean break to be made with the past. The choice is left to 
+the community of the incoming project.
+          </p>
+<p>
+The infrastructure team will perform the import including
+mapping IDs but it is an operation that requires skill, time and care. In this case, 
+please ask the infrastructure team politely.
+          </p>
+</div>
 </div>
 <h4>
    <a name="crypto-audit">Audit Cryptography</a>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message