openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r1467457 - in /openjpa/site/trunk/content: apache-nexus-release-process-(1.2.x-2.1.x).mdtext release-setup.mdtext
Date Fri, 12 Apr 2013 20:45:07 GMT
Author: allee8285
Date: Fri Apr 12 20:45:07 2013
New Revision: 1467457

URL: http://svn.apache.org/r1467457
Log:
Fix release set up typos

Modified:
    openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
    openjpa/site/trunk/content/release-setup.mdtext

Modified: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.mdtext?rev=1467457&r1=1467456&r2=1467457&view=diff
==============================================================================
--- openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext (original)
+++ openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext Fri Apr 12
20:45:07 2013
@@ -211,7 +211,7 @@ Different arguments and steps are requir
     3. Perform a review of the release and cast your vote. See the following for more details
on Apache releases -
         1. [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
         1. [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
-    4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually
a good idea to rollback the release if a -1 vote is received. See - [*Recovering from a vetoed
release](*recovering-from-a-vetoed-release.html)
+    4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually
a good idea to rollback the release if a -1 vote is received. See - [Recovering from a vetoed
release](#recoverFromVetoRelease)
     5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes
and no -1 votes, then post the results to the vote thread by -
         1. Reply to the initial email and prepend to the original subject -
  
@@ -267,21 +267,25 @@ Different arguments and steps are requir
     4. Update the [JIRA Releases](https://issues.apache.org/jira/browse/OPENJPA) page to
mark the version as "released", and set the date to the date that the release was approved.
You may also need to make a new release entry for the next release.
     
 12. Update wiki pages
-    1. After the distribution and build files have been mirrored out to the external sites
(takes about an hour), update the [Downloads](/downloads.html) and [Documentation](/documentation.html)
pages with the new release.
+    1. After the distribution and build files have been mirrored out to the external sites
(takes about an hour), update the [Downloads](downloads.html) and [Documentation](documentation.html)
pages with the new release.
     2. Make a blog announcement on the OpenJPA wiki. 
         1. FIX ME!
 
 13. Announcing the release
-    1. FIX MEEEE After the Maven mirrors have had time to update (24 hours to be on the safe
side) and the wiki updates have been exported and mirrored to the external website, then it's
time to announce the release.  Make an announcement about the release on the dev@, user@ and
[mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html*foundation-announce]
+    1. FIX MEEEE!!  After the Maven mirrors have had time to update (24 hours to be on the
safe side) and the wiki updates have 
+    been exported and mirrored to the external website, then it's time to announce the release.
Make an announcement about 
+    the release on the dev@, user@ and [mailto:announce@apache.org] list as per 
+    [the Apache Announcement Mailing Lists page](http://www.apache.org/foundation/mailinglists.html#foundation-announce)
 )
 
-        <span class="note">
+        <div class="note">
 Make sure you send the announcement to announce@apache.org from your
 user@apache.org. This can be achieved using gmail by setting the "From"
 field to user@apche.org instead of user@gmail.com when sending the
-announcement.</span>
+announcement.
+</div>
     
- 
+<a name="recoverFromVetoRelease"></a> 
 # Recovering from a vetoed release
 1. Reply to the initial vote email and prepend to the original subject -
 

Modified: openjpa/site/trunk/content/release-setup.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-setup.mdtext?rev=1467457&r1=1467456&r2=1467457&view=diff
==============================================================================
--- openjpa/site/trunk/content/release-setup.mdtext (original)
+++ openjpa/site/trunk/content/release-setup.mdtext Fri Apr 12 20:45:07 2013
@@ -5,7 +5,8 @@ These setup steps only need to be perfor
  
 <table class="info"><tr>
   <td valign="top"><img src="images/information.gif" width="16" height="16" border="0">
-  <td>Developers using Linux workstations can skip over the references to Cygwin. 
If using Windows, install cygwin, including **Utils/gnupg** and **Net/openssh** packages.
+  <td>Developers using Linux workstations can skip over the references to Cygwin. 
If using Windows, install cygwin, including <b>Utils/gnupg</b> and <b>Net/openssh</b>
packages.<br/><br/>
+  See <a href="http://www.gnupg.org/gph/en/manual.html">GNU Privacy Handbook</a>
for a quick start on the basic concepts.
 </tr></table>
 
 <a name="ReleaseSetup-CreateandinstallaSSHkey"></a>
@@ -55,9 +56,9 @@ These setup steps only need to be perfor
     <td valign="top"><img src="images/information.gif" width="16" height="16" border="0">
     <td>
     
-   * Each public key in the {{authorized_keys}} spans only one line. For example:
+   * Each public key in the **`authorized_keys`**<a name="ReleaseSetup-CreateandinstallaSSHkey"></a>
spans only one line. For example:
              
-          "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107}}"
+          "ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107"
             
    * '#' in the first column is a comment line.
     </tr></table>
@@ -142,8 +143,8 @@ These setup steps only need to be perfor
     </tr></table>
     
 1. Backup your cygwin home directory to another media
-1. Append your public key to {{[https://svn.apache.org/repos/asf/openjpa/KEYS](https://svn.apache.org/repos/asf/openjpa/KEYS)
-}} and <http://www.apache.org/dist/openjpa/KEYS>. See the commands describe at the
beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published
artifacts for the releases.
+1. Append your public key to [https://svn.apache.org/repos/asf/openjpa/KEYS](https://svn.apache.org/repos/asf/openjpa/KEYS)
+ and <http://www.apache.org/dist/openjpa/KEYS>. See the commands describe at the beginning
of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts
for the releases.
  
         $ ( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name>
) >> KEYS
 
@@ -151,7 +152,7 @@ These setup steps only need to be perfor
       <td valign="top"><img src="images/information.gif" width="16" height="16"
border="0">
       <td>
 
-    * The {{<https://svn.apache.org/repos/asf/openjpa/KEYS> }} file is updated via
normal svn commit procedures.
+    * The <https://svn.apache.org/repos/asf/openjpa/KEYS> file is updated via normal
svn commit procedures.
 
             svn co https://svn.apache.org/repos/asf/openjpa --depth empty
             cd openjpa



Mime
View raw message