incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r892083 - in /websites/staging/incubator/trunk/content: ./ guides/releasemanagement.html report-next-month.html sitemap.html
Date Sun, 29 Dec 2013 18:33:06 GMT
Author: buildbot
Date: Sun Dec 29 18:33:05 2013
New Revision: 892083

Log:
Staging update by buildbot for incubator

Modified:
    websites/staging/incubator/trunk/content/   (props changed)
    websites/staging/incubator/trunk/content/guides/releasemanagement.html
    websites/staging/incubator/trunk/content/report-next-month.html
    websites/staging/incubator/trunk/content/sitemap.html

Propchange: websites/staging/incubator/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Dec 29 18:33:05 2013
@@ -1 +1 @@
-1553972
+1554052

Modified: websites/staging/incubator/trunk/content/guides/releasemanagement.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/releasemanagement.html (original)
+++ websites/staging/incubator/trunk/content/guides/releasemanagement.html Sun Dec 29 18:33:05
2013
@@ -220,10 +220,6 @@ Archiving
 Security
  </a>
  <ul>
-<li><a href='#distribution-permissions'>
-Permissions
- </a>
-</li>
 <li><a href='#distribution-checksums-sigs'>
 Sums And Signatures
  </a>
@@ -772,7 +768,7 @@ For example, the podling distribution di
         <code>www.apache.org/dist/incubator/{podling}</code>. 
         </li>
         <li>
-        Infrastructure insists that releases are mirrored, permissions are correct and that
+        Infrastructure insists that releases are mirrored and that
         <a href="http://www.apache.org/dev/release-signing.html#keys-policy">signatures+checksums</a>

         are uploaded for every artifact. 
         </li>
@@ -792,6 +788,7 @@ For example, the podling distribution di
         guide for the podling.
         </p>
 </div>
+<a id="distribution-permissions" />
 <h3 id='understanding-distribution'>Understanding Release Distribution</h3>
 <div class="section-content">
 <h4 id='understanding-upload'>Uploading Artifacts</h4>
@@ -870,41 +867,6 @@ For example, the podling distribution di
 </div>
 <h4 id='understanding-security'>Security</h4>
 <div class="section-content">
-<h5 id='distribution-permissions'>Permissions</h5> 
-<div class="section-content">
-<p>
-        One group is created by infrastructure for each top level project. All releases 
-        by the project should be owned by that group. This group should have read
-        and write permissions. This ensures that each project can manage its own releases.

-        The world should have only read only permissions to avoid accidental modification.
-        In short <code>-rw-rw-r--</code>.
-            </p>
-<p>
-        Each podling release is a release of the Incubator project. So, all files should

-        be:
-            </p>
-<ul>
-        <li>owned by the <code>incubator</code> group</li>
-        <li>be group writable</li>
-        <li>be read only for the world</li>
-            </ul>
-<p>
-        To do this from the top level:
-            </p>
-<div class="source"><code>
-        &gt; find . -type f -exec chmod 664 {} \;
-        &gt; find . -type d -exec chmod 775 {} \;
-        &gt; chgrp -R incubator *
-            </code>
-</div>
-<p>
-        When a podling graduates to a top level project, a new group will be created. 
-        New releases will then use that group (as well as being located in a subdirectory

-        of <code>dist</code> rather than <code>dist/incubator</code>).
-        If a podling graduates as a subproject then the group of its new parent project
-        will then be used.
-            </p>
-</div>
 <h5 id='distribution-checksums-sigs'>Sums And Signatures</h5> 
 <div class="section-content">
 <p>
@@ -963,7 +925,6 @@ For example, the podling distribution di
 <ul>
           <li>Directory is <code>www.apache.org/dist/incubator/<em>podling</em></code></li>
           <li>Group is <code>incubator</code></li>
-          <li>Permissions are group writable and world read-only</li>
           <li>All artifacts have matching checksums and signatures</li>
           <li>Old releases archived</li>
           <li>Links to <code>KEYS</code>, signature and checksum documents

Modified: websites/staging/incubator/trunk/content/report-next-month.html
==============================================================================
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Sun Dec 29 18:33:05 2013
@@ -67,7 +67,7 @@
 <h1>
 <a href="http://incubator.apache.org">Apache Incubator</a> Podlings needing to
prepare report for January</h1>
 <div style="text-align:right;">
-<i>Generated on 2013-12-28T23:28:34Z</i>
+<i>Generated on 2013-12-29T18:32:44Z</i>
 </div>
 <nav>
 <ul>

Modified: websites/staging/incubator/trunk/content/sitemap.html
==============================================================================
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Sun Dec 29 18:33:05 2013
@@ -1255,9 +1255,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#understanding-security">Security</a>
 <ul>
 <li>
-<a href="guides/releasemanagement.html#distribution-permissions">Permissions</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#distribution-checksums-sigs">Sums And Signatures</a>
 </li>
 <li>



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


Mime
View raw message