incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r609289 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Sun, 06 Jan 2008 10:52:10 GMT
Author: rdonkin
Date: Sun Jan  6 02:52:02 2008
New Revision: 609289

URL: http://svn.apache.org/viewvc?rev=609289&view=rev
Log:
Introduced term podling distribution directory defined in the glossary. Hope that this will
make it easier to understand.

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

Modified: incubator/public/trunk/site-author/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/releasemanagement.xml?rev=609289&r1=609288&r2=609289&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Sun Jan  6 02:52:02 2008
@@ -198,7 +198,7 @@
         The Incubator 
         <a href='/incubation/Incubation_Policy.html#Releases'>insists</a> 
         that artifacts for <em>podling</em> are contained within
-        <code>www.apache.org/dist/incubator/podling</code>. 
+        <code>www.apache.org/dist/incubator/<em>podling</em></code>.

         </li>
         <li>
         Infrastructure insists that releases are mirrored, permissions are correct and that
@@ -220,10 +220,18 @@
           <p>
           The distribution upload location (<code>www.apache.org/dist</code>)
for all Apache projects is the
           <code>/www/www.apache.org/dist</code> directory on <code>people.apache.org</code>.
-          Each project (including the incubator) owns a directory inside the
-          dist directory. Podlings own a directory inside the incubator
-          directory.
-          Release artifacts should be copied into this position in the normal way.
+          Each project (including the Incubator) owns a directory within <code>dist</code>.

+          </p><p>
+          The <a href='#glossary-podling-dist'>podling distribution directory</a>
+          is contained within this <a href='#glossary-incubator-dist'>Incubator distribution
directory</a>.
+          The <a href='http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
Project Management Committee (IPMC)</a> 
+          is responsible for all releases.
+          Arrangement and management of releases within each podling distribution directory
+          is delegated to the appropriate podling.
+          </p><p>
+          Release artifacts can be uploaded into the podling distribution directory
+          using <a href='http://www.apache.org/dev/user-ssh.html'>scp</a>. It
is best
+          to <code>scp</code> into the home directory and then copy into position
from there.
           </p>
         </section>
         <section id='understanding-mirroring'><title>Mirroring</title>
@@ -272,7 +280,7 @@
           <section id='distribution-permissions'><title>Permissions</title>
             <p>
         One group is created by infrastructure for each top level project. All releases 
-        by that project should be owned by that group. This group should have read
+        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>.
@@ -295,8 +303,8 @@
             </source>
             <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 top level 
-        subdirectory of <code>dist</code> rather than <code>dist/incubator</code>).
+        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>
@@ -357,7 +365,8 @@
         <section id='distribution-layout'><title>Layout</title>
           <p>
             A podling is free to choose a suitable layout for its released
-            artifacts within <code>www.apache.org/dist/incubator/<em>podling</em></code>.
+            artifacts within the 
+            <a href='#glossary-podling-dist'>podling distribution directory</a>
.
             It is recommended that standard layouts (commonly used by other projects) 
             be studied and that the layout adopted is documented in the podling's 
             release documentation. The descriptions which follow can be used as a 
@@ -369,21 +378,24 @@
           </p>
           <section id='distribution-layout-plain'><title>Plain Artifacts</title>
             <p>
-          All artifacts, checksums and signatures should be placed in
-          <code>www.apache.org/dist/incubator/<em>podling</em></code>.
No release
-          documentation is placed within the distribution directory.
+          All artifacts, checksums and signatures placed directly into the
+          <a href='#glossary-podling-dist'>podling distribution directory</a>.
+          No subdirectories are created. 
+          No <a href='#distribution-release-documentation'>release documentation</a>

+          is placed within the distribution directory.
             </p>
           </section>
           <section id='distribution-layout-misc'><title>Miscellaneous Documents</title>
             <p>
             All files contained in <code>www.apache.org/dist</code> will be mirrored.
-            So, other documents placed in the distribution directories will be 
-            available on the mirrors for those casual browsers.
+            So, in addition in archives other documents placed in the distribution 
+            directories will be available on the mirrors for casual browsing.
             </p><p>
             As is traditional in some communities, some like to add notices 
             (such as <code>RELEASE_NOTES</code>, <code>README</code>

             and <code>CHANGES</code>) for each release. Note that from publicity
-            perspective it may be effective to include this information on the download page
as well as in the release itself.
+            perspective it may be effective to include this information on the 
+            download page as well as in the release itself.
             </p><p>
             The HTTPD runs with fancy indexing enabled. So, creating <code>HEADER.html</code>
and
             <code>FOOTER.html</code> documents allows the text of the index page
to be customised.
@@ -518,8 +530,8 @@
           <p>
           Each podling should maintain its own 
           <a href='http://www.apache.org/dev/release-signing.html#keys-policy'>KEYS</a>

-          file in the root its subdirectory. All committers for the podling are encouraged

-          to add their keys to their file.
+          file directly in the <a hred='#glossary-podling-dist'>podling distribution
directory</a>. 
+          It is recommended that all committers add their keys to that file.
           </p>
         </section>
         <section id='distribution-defects'><title>Dealing With A Defect</title>
@@ -2079,6 +2091,38 @@
  <a href='http://www.apache.org/dev/#pmc'>Apache information for PMCs</a>
                 </li>
              </ul>
+        </section>
+        <section id='glossary-incubator-dist'><title>Incubator Distribution Directory</title>
+          <p>
+All Incubator authorised by the incubator are contained within the
+Incubator distribution directory:
+          </p>
+<source>
+www.apache.org/dist/incubator
+</source>
+        </section>
+        <section id='glossary-podling-dist'><title>Podling Distribution Directory</title>
+          <p>
+All releases created by a podling are contained within a sub-directory of the
+<a href='#glossary-incubator-dist'>Incubator distribution directory</a>.
+This is <code>www.apache.org/dist/incubator/<em>podling</em></code>
where <em>podling</em> 
+is the name of the podling.
+          </p>
+          <p>
+For example, the podling distribution directory for podling <code>foo</code>
is
+<code>www.apache.org/dist/incubator/foo</code>.
+          </p>
+          <p>
+See also:
+          </p>
+          <ul>
+            <li>
+            <a href='#distribution-policy-overview'>Distribution policy overview</a>
+            </li>
+            <li>
+            <a href='#understanding-upload'>Uploading distributions</a>
+            </li>
+          </ul>
         </section>
     </section>
   </body>

Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?rev=609289&r1=609288&r2=609289&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Sun Jan  6 02:52:02
2008
@@ -605,6 +605,14 @@
 Project Management Committee
  </a>
 </li>
+<li><a href='#glossary-incubator-dist'>
+Incubator Distribution Directory
+ </a>
+</li>
+<li><a href='#glossary-podling-dist'>
+Podling Distribution Directory
+ </a>
+</li>
 </ul>
 </li>
 </ul>
@@ -745,7 +753,7 @@
         The Incubator 
         <a href="/incubation/Incubation_Policy.html#Releases">insists</a> 
         that artifacts for <em>podling</em> are contained within
-        <code>www.apache.org/dist/incubator/podling</code>. 
+        <code>www.apache.org/dist/incubator/<em>podling</em></code>.

         </li>
         <li>
         Infrastructure insists that releases are mirrored, permissions are correct and that
@@ -773,10 +781,20 @@
 <p>
           The distribution upload location (<code>www.apache.org/dist</code>)
for all Apache projects is the
           <code>/www/www.apache.org/dist</code> directory on <code>people.apache.org</code>.
-          Each project (including the incubator) owns a directory inside the
-          dist directory. Podlings own a directory inside the incubator
-          directory.
-          Release artifacts should be copied into this position in the normal way.
+          Each project (including the Incubator) owns a directory within <code>dist</code>.

+          </p>
+<p>
+          The <a href="#glossary-podling-dist">podling distribution directory</a>
+          is contained within this <a href="#glossary-incubator-dist">Incubator distribution
directory</a>.
+          The <a href="http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
Project Management Committee (IPMC)</a> 
+          is responsible for all releases.
+          Arrangement and management of releases within each podling distribution directory
+          is delegated to the appropriate podling.
+          </p>
+<p>
+          Release artifacts can be uploaded into the podling distribution directory
+          using <a href="http://www.apache.org/dev/user-ssh.html">scp</a>. It
is best
+          to <code>scp</code> into the home directory and then copy into position
from there.
           </p>
 </div>
 <h4>
@@ -839,7 +857,7 @@
 <div class="section-content">
 <p>
         One group is created by infrastructure for each top level project. All releases 
-        by that project should be owned by that group. This group should have read
+        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>.
@@ -864,8 +882,8 @@
 </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 top level 
-        subdirectory of <code>dist</code> rather than <code>dist/incubator</code>).
+        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>
@@ -946,7 +964,8 @@
 <div class="section-content">
 <p>
             A podling is free to choose a suitable layout for its released
-            artifacts within <code>www.apache.org/dist/incubator/<em>podling</em></code>.
+            artifacts within the 
+            <a href="#glossary-podling-dist">podling distribution directory</a>
.
             It is recommended that standard layouts (commonly used by other projects) 
             be studied and that the layout adopted is documented in the podling's 
             release documentation. The descriptions which follow can be used as a 
@@ -962,9 +981,11 @@
 </h5> 
 <div class="section-content">
 <p>
-          All artifacts, checksums and signatures should be placed in
-          <code>www.apache.org/dist/incubator/<em>podling</em></code>.
No release
-          documentation is placed within the distribution directory.
+          All artifacts, checksums and signatures placed directly into the
+          <a href="#glossary-podling-dist">podling distribution directory</a>.
+          No subdirectories are created. 
+          No <a href="#distribution-release-documentation">release documentation</a>

+          is placed within the distribution directory.
             </p>
 </div>
 <h5> 
@@ -973,14 +994,15 @@
 <div class="section-content">
 <p>
             All files contained in <code>www.apache.org/dist</code> will be mirrored.
-            So, other documents placed in the distribution directories will be 
-            available on the mirrors for those casual browsers.
+            So, in addition in archives other documents placed in the distribution 
+            directories will be available on the mirrors for casual browsing.
             </p>
 <p>
             As is traditional in some communities, some like to add notices 
             (such as <code>RELEASE_NOTES</code>, <code>README</code>

             and <code>CHANGES</code>) for each release. Note that from publicity
-            perspective it may be effective to include this information on the download page
as well as in the release itself.
+            perspective it may be effective to include this information on the 
+            download page as well as in the release itself.
             </p>
 <p>
             The HTTPD runs with fancy indexing enabled. So, creating <code>HEADER.html</code>
and
@@ -1139,8 +1161,8 @@
 <p>
           Each podling should maintain its own 
           <a href="http://www.apache.org/dev/release-signing.html#keys-policy">KEYS</a>

-          file in the root its subdirectory. All committers for the podling are encouraged

-          to add their keys to their file.
+          file directly in the <a hred="#glossary-podling-dist">podling distribution
directory</a>. 
+          It is recommended that all committers add their keys to that file.
           </p>
 </div>
 <h4>
@@ -2976,6 +2998,45 @@
  <a href="http://www.apache.org/dev/#pmc">Apache information for PMCs</a>
                 </li>
              </ul>
+</div>
+<h3>
+   <a name="glossary-incubator-dist">Incubator Distribution Directory</a>
+</h3>
+<div class="section-content">
+<p>
+All Incubator authorised by the incubator are contained within the
+Incubator distribution directory:
+          </p>
+<div class="source"><code>
+www.apache.org/dist/incubator
+</code>
+</div>
+</div>
+<h3>
+   <a name="glossary-podling-dist">Podling Distribution Directory</a>
+</h3>
+<div class="section-content">
+<p>
+All releases created by a podling are contained within a sub-directory of the
+<a href="#glossary-incubator-dist">Incubator distribution directory</a>.
+This is <code>www.apache.org/dist/incubator/<em>podling</em></code>
where <em>podling</em> 
+is the name of the podling.
+          </p>
+<p>
+For example, the podling distribution directory for podling <code>foo</code>
is
+<code>www.apache.org/dist/incubator/foo</code>.
+          </p>
+<p>
+See also:
+          </p>
+<ul>
+            <li>
+            <a href="#distribution-policy-overview">Distribution policy overview</a>
+            </li>
+            <li>
+            <a href="#understanding-upload">Uploading distributions</a>
+            </li>
+          </ul>
 </div>
 </div>
          </td>



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


Mime
View raw message