You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2018/06/22 11:01:48 UTC

svn commit: r1031605 - in /websites/staging/jena/trunk/content: ./ getting_involved/reviewing_contributions.html

Author: buildbot
Date: Fri Jun 22 11:01:48 2018
New Revision: 1031605

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 22 11:01:48 2018
@@ -1 +1 @@
-1833568
+1834108

Modified: websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html (original)
+++ websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html Fri Jun 22 11:01:48 2018
@@ -221,6 +221,12 @@ Where this comes into play is when a lar
 <p>A pull request is a single unit so a large number of commits details the evolution internally
 but does not help record the external contribution.</p>
 <p>Consider asking the contributor to merge commits into a few with useful messages for an external reviewer.</p>
+<h2 id="project-processes">Project Processes<a class="headerlink" href="#project-processes" title="Permanent link">&para;</a></h2>
+<p><a href="https://cwiki.apache.org/confluence/display/JENA/Processes">Project Processes</a> including:</p>
+<ul>
+<li>[Release process](https://cwiki.apache.org/confluence/display/JENA/Release+Process</li>
+<li><a href="https://cwiki.apache.org/confluence/display/JENA/Commit+Workflow+for+Github-ASF">Commit Workflow for Github-ASF</a></li>
+</ul>
   </div>
 </div>