Repository: apex-site
Updated Branches:
  refs/heads/asf-site ff1150891 -> d2f45dd73


from 9bb952452df11d94c4d01828045a96d153c8b7d2


Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/d2f45dd7
Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/d2f45dd7
Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/d2f45dd7

Branch: refs/heads/asf-site
Commit: d2f45dd73c63d3c9ed0462f0fe523c7c876c0913
Parents: ff11508
Author: Apex Dev <[email protected]>
Authored: Fri Mar 31 23:45:37 2017 -0700
Committer: Thomas Weise <[email protected]>
Committed: Fri Mar 31 23:45:37 2017 -0700

----------------------------------------------------------------------
 content/release.html | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/apex-site/blob/d2f45dd7/content/release.html
----------------------------------------------------------------------
diff --git a/content/release.html b/content/release.html
index 591caab..865c3d9 100644
--- a/content/release.html
+++ b/content/release.html
@@ -249,7 +249,6 @@ git push apache
 </code></pre>
 <p>Cherry-pick <code>@since</code> tag and change log changes from release tag 
to <code>master</code>.</p>
 <h3 id="documentation">Documentation</h3>
-<p>There two steps in promotion. The documentation built during the build step 
above is made available on the website and then any changes to the rest of the 
website are deployed.</p>
 <p>If this is a minor or a major release, link the release documentation as 
latest on the web site. Otherwise it is a patch release and this step can be 
skipped (documentation is already reflected in the website).</p>
 <p>Under the <code>apex-site</code> folder (<code>asf-site</code> branch):</p>
 <pre><code class="lang-bash"># docv major.minor version calculated in the 
build step

Reply via email to