svn commit: r1485990 - /sling/site/trunk/content/documentation/development/release-management.mdtext

[bd...@apache.org]

Author: bdelacretaz
Date: Fri May 24 09:49:53 2013
New Revision: 1485990

URL: http://svn.apache.org/r1485990
Log:
fix formatting

Modified:
    sling/site/trunk/content/documentation/development/release-management.mdtext

Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1485990&r1=1485989&r2=1485990&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Fri May 24 09:49:53 2013
@@ -94,7 +94,7 @@ Then, close the staging repository:
   * Verify the staged artifacts
     * If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then rollback your release (see *Canceling the Release*) and repeat the process
     
-Note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email
+Note the staging repository URL, especially the number at the end of the URL. You will need this in your vote email
 
 ## Starting the Vote
 
@@ -136,8 +136,13 @@ Propose a vote on the dev list with the 
 
 From [Votes on Package Releases](http://www.apache.org/foundation/voting.html):
 
-{quote}Votes on whether a package is ready to be released follow a format similar to majority approval -- except that the decision is officially determined solely by whether at least three \+1 votes were registered. Releases may not be vetoed. Generally the community will table the vote to release if anyone identifies serious problems, but in most cases the ultimate decision, once three or more positive votes have been garnered, lies with the individual serving as release manager. The specifics of the process may vary from project to project, but the 'minimum of three \+1 votes' rule is universal.{quote}
-
+> Votes on whether a package is ready to be released follow a format similar to majority 
+> approval -- except that the decision is officially determined solely by whether at least 
+> three \+1 votes were registered. Releases may not be vetoed. Generally the community 
+> will table the vote to release if anyone identifies serious problems, but in most cases 
+> the ultimate decision, once three or more positive votes have been garnered, lies with 
+> the individual serving as release manager. The specifics of the process may vary from 
+> project to project, but the 'minimum of three \+1 votes' rule is universal.
 
 The list of binding voters is available on the [Project Team]({{ refs.project-team.path }}) page.