incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From johndam...@apache.org
Subject svn commit: r1776598 - in /incubator/public/trunk/content: 2017-logo-contest.xml guides/draft-simple-release-management.xml
Date Fri, 30 Dec 2016 16:10:11 GMT
Author: johndament
Date: Fri Dec 30 16:10:11 2016
New Revision: 1776598

URL: http://svn.apache.org/viewvc?rev=1776598&view=rev
Log:
Updating logo page to remove instance.
Updating release management page with clearer text.

Modified:
    incubator/public/trunk/content/2017-logo-contest.xml
    incubator/public/trunk/content/guides/draft-simple-release-management.xml

Modified: incubator/public/trunk/content/2017-logo-contest.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/2017-logo-contest.xml?rev=1776598&r1=1776597&r2=1776598&view=diff
==============================================================================
--- incubator/public/trunk/content/2017-logo-contest.xml [utf-8] (original)
+++ incubator/public/trunk/content/2017-logo-contest.xml [utf-8] Fri Dec 30 16:10:11 2016
@@ -60,7 +60,7 @@ limitations under the License.
                 <p>
                     Here are some straight forward steps to submit your logo
                     <ul>
-                        <li>Create an account on the <a href="https://issues.apache.org/jira/secure/Signup!default.jspa"
target="_new">ASF JIRA Instance</a> (if you don't already have one)</li>
+                        <li>Create an account on the <a href="https://issues.apache.org/jira/secure/Signup!default.jspa"
target="_new">ASF JIRA</a> (if you don't already have one)</li>
                         <li>Create an issue on the <a href="https://issues.apache.org/jira/secure/CreateIssue.jspa?selectedProjectId=10595&amp;issuetype=3"
target="_new">Incubator Project</a></li>
                         <li>Click Next</li>
                         <li>Create a ticket, with the following information:

Modified: incubator/public/trunk/content/guides/draft-simple-release-management.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/draft-simple-release-management.xml?rev=1776598&r1=1776597&r2=1776598&view=diff
==============================================================================
--- incubator/public/trunk/content/guides/draft-simple-release-management.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/draft-simple-release-management.xml [utf-8] Fri
Dec 30 16:10:11 2016
@@ -66,13 +66,15 @@ limitations under the License.
                 </p>
                 <p>
                     It is well understood that one of the goals of incubation is to help
a podling understand how to
-                    build ASF compliant releases.  This is why its important to have
-                    <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">mentors</a>
-                    and other
+                    build <a href="http://www.apache.org/dev/#releases">ASF compliant
releases</a>. This is why its
+                    mandatory to have at least 3 +1 votes from
                     <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC
members</a>
-                    review the releases for accuracy in compliance with the ASF and Incubator
policies.  Those reviewing the releases will provide the release managers
-                    with information about what is wrong with the release.  Release managers
should consider issues reported as blocking, unless told otherwise
-                    by those reporting the issue.
+                    review the releases (this should include your <a href="&root-path;/incubation/Roles_and_Responsibilities.html#Mentor">mentors</a>
but is not mandatory)
+                    for accuracy in compliance with the ASF and <a href="&root-path;/incubation/Incubation_Policy.html#Releases">Incubator
policies</a>.
+                    The podling community, of course, needs to be fully engaged in review
process as well. Anybody reviewing
+                    the releases will provide the release manager and IPMC members with information
about what is wrong
+                    with the release. The severity of the issues and whether they are blocking
or not may be discussed
+                    but the ultimate guidance on where podling releases may get additional
flexibility belongs to the mentors and IPMC members.
                 </p>
             </section>
             <section id="podling-constraints">



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


Mime
View raw message