This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/attic.git


The following commit(s) were added to refs/heads/main by this push:
     new 728308c  ATTIC-240 we now use Git
728308c is described below

commit 728308caeb80894e082e1eccae43d15d9e1090bb
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Sun Apr 20 17:30:50 2025 +0200

    ATTIC-240 we now use Git
---
 .gitignore        |  1 +
 retire.py         |  6 +++---
 xdocs/process.xml | 19 +++++++++----------
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/.gitignore b/.gitignore
index 84e50f3..9607d07 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 asf-site/
 .svn-legacy/
+*.tmp
diff --git a/retire.py b/retire.py
index 1932486..fdb2970 100755
--- a/retire.py
+++ b/retire.py
@@ -164,7 +164,7 @@ def create_project(pid):
         description = meta.get('description', 'TBA'))
     with open(outfile, 'w', encoding='utf-8') as o:
         o.write(out)
-    os.system("svn add %s" % outfile)
+    os.system("git add %s" % outfile)
     print("Check XML file for customisations such as JIRA and mailing lists")
 
 def find_wiki(pid):
@@ -182,7 +182,7 @@ def check_wiki(pid):
             if not flagname == pid:
                 w.write(pid)
                 w.write("\n")
-        os.system("svn add %s" % flagfile)
+        os.system("git add %s" % flagfile)
 
 for arg in sys.argv[1:]:
     print("Processing "+arg)
@@ -196,7 +196,7 @@ for arg in sys.argv[1:]:
     create_jira_template(arg)
     os.mkdir(flagdir)
     open(join(flagdir, "git.keep"), 'a').close()
-    os.system("svn add %s" % flagdir)
+    os.system("git add %s" % flagdir)
     create_project(arg)
     update_stylesheet(arg)
     check_wiki(arg)
diff --git a/xdocs/process.xml b/xdocs/process.xml
index ee06538..bbb6b91 100644
--- a/xdocs/process.xml
+++ b/xdocs/process.xml
@@ -42,7 +42,7 @@
       </ul>
     </li>
     <li>If the board approves the resolution, open an <a 
href="https://issues.apache.org/jira/browse/ATTIC";>Attic JIRA</a> item - 'Move 
${project} to the Attic'.<br />
-      The Attic PMC will step in and create a detailed issue description using 
<a 
href="https://svn.apache.org/repos/asf/attic/site/retire.py";><code>retire.py</code></a>,
 with other generated parts to move the project to the Attic.<br />
+      The Attic PMC will step in and create a detailed issue description using 
<a 
href="https://github.com/apache/attic/blob/main/retire.py";><code>retire.py</code></a>,
 with other generated parts to move the project to the Attic.<br />
       Generated issue content typically contains following steps (see <a 
href="#howto">"How to"</a> below for a description of each step): 
       <ol type="1">
         <li><a href="#confirm-resolution">#</a> Confirm Board Resolution</li>
@@ -125,10 +125,10 @@ ${Name} on behalf of ${project} + the Attic.
   <title>How to: 3. Create project page on Attic site: 
https://attic.apache.org/projects/${project}.html</title>
 
   <p>The Attic website is built using Anakia. <a 
href="https://velocity.apache.org/anakia/";>Anakia</a> is an old site technology 
built on top of Apache Velocity. 
-     You can get the source for the site from Subversion: </p>
-  <pre>svn co https://svn.apache.org/repos/asf/attic/site</pre>
+     You can get the source for the site from Git: </p>
+  <pre>git clone https://github.com/apache/attic</pre>
 
-  <p>You can generate the required changes using the Python3 <a 
href="https://svn.apache.org/repos/asf/attic/site/retire.py";><code>retire.py</code></a>
 script as follows:</p>
+  <p>You can generate the required changes using the Python3 <a 
href="https://github.com/apache/attic/blob/main/retire.py";><code>retire.py</code></a>
 script as follows:</p>
   <pre>./retire.py id1 [id2...]</pre>
   <p>This should generate the following files for each ID, as well as updating 
<code>xdocs/stylesheets/project.xml</code>:</p>
   <ul>
@@ -137,10 +137,9 @@ ${Name} on behalf of ${project} + the Attic.
     <li><code>xdocs/projects/ID.xml</code></li>
     <li><code>cwiki_retired/WIKI_ID.txt</code> (this adds the CWIKI banner for 
projects)</li>
   </ul>
-  <p>The code allows for wiki aliases, as described in the 
cwiki_retired/AAREADME.txt file.</p>
-  <p>Review the changes in <code>xdocs/</code>, then commit to svn.</p>
-  <p>The <code>ID.jira.tmp</code> file is text that can be copy-pasted into a 
JIRA description. It should be deleted after use, and not committed to SVN.</p>
-  <p>The <a href="https://ci2.apache.org/#/builders/16";>buildbot job</a> will 
build the site and commit the result which will be published soon after.</p>
+  <p>The code allows for wiki aliases, as described in the 
<code>cwiki_retired/AAREADME.txt</code> file.</p>
+  <p>Review the changes in <code>xdocs/</code>, then commit to Git.</p>
+  <p>The <code>ID.jira.tmp</code> file is text that can be copy-pasted into a 
JIRA description. It should be deleted after use, and not committed to Git.</p>
 </section>
 
 <section id="doap">
@@ -171,7 +170,7 @@ new category:  &lt;category 
rdf:resource="http://projects.apache.org/category/re
   <title>How to: 5. Get infra lock down project's resources</title>
   <p>Open an <a 
href="https://issues.apache.org/jira/browse/INFRA";>Infrastructure JIRA</a> 
issue identifying the resources that need turning off/making read only.</p>
 
-  <p>The content of the issue can be generated using <a 
href="https://svn.apache.org/repos/asf/attic/site/infrajiratext.py";><code>infrajiratext.py</code></a>.</p>
+  <p>The content of the issue can be generated using <a 
href="hhttps://github.com/apache/attic/blob/main/infrajiratext.py";><code>infrajiratext.py</code></a>.</p>
 
   <p>Typically, it contains steps like following, that need to be tweaked 
based on assets of the retired project:
     <ul>
@@ -226,7 +225,7 @@ on behalf of the Apache Attic and the now retired Apache 
${project} project
   </pre>
 
   <p>It's important to include the boilerplate from the project's site so 
people 
-     know what we're talking about. </p>
+     know what we're talking about.</p>
 </section>
 
 </body>

Reply via email to