beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@apache.org
Subject [3/4] beam-site git commit: Regenerate website
Date Wed, 28 Dec 2016 01:38:08 GMT
Regenerate website


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

Branch: refs/heads/asf-site
Commit: 99e1fb131bcb672286e2696fed2f9693964c43bc
Parents: 58cf95d
Author: Davor Bonaci <davor@google.com>
Authored: Tue Dec 27 17:37:38 2016 -0800
Committer: Davor Bonaci <davor@google.com>
Committed: Tue Dec 27 17:37:38 2016 -0800

----------------------------------------------------------------------
 content/contribute/release-guide/index.html | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/beam-site/blob/99e1fb13/content/contribute/release-guide/index.html
----------------------------------------------------------------------
diff --git a/content/contribute/release-guide/index.html b/content/contribute/release-guide/index.html
index 9e7c8e7..74d3b96 100644
--- a/content/contribute/release-guide/index.html
+++ b/content/contribute/release-guide/index.html
@@ -536,18 +536,13 @@ TAG="v${VERSION}-RC${RC_NUM}"
 
 <p>The final step of building the candidate is to propose a website pull request.</p>
 
-<p>Add the new release to the <a href="/use/releases/">Apache Beam Releases</a>
page, as follows:</p>
+<p>Start by updating <code class="highlighter-rouge">release_latest</code>
version flag in the top-level <code class="highlighter-rouge">_config.yml</code>,
and list the new release in the <a href="/get-started/downloads/">Apache Beam Downloads</a>,
linking to the source code download and the Release Notes in JIRA.</p>
 
-<ul>
-  <li>Update the <code class="highlighter-rouge">&lt;version&gt;</code>
tags in the sample <code class="highlighter-rouge">pom.xml</code> snippet to the
new release.</li>
-  <li>Add the new version to the <code class="highlighter-rouge">Release Notes</code>
section below, along with links to the source code download and the Release Notes in JIRA.</li>
-</ul>
-
-<p>Add the new Javadoc to <a href="/learn/sdks/javadoc/">SDK API Reference page</a>
page, as follows:</p>
+<p>Add the new Javadoc to <a href="/documentation/sdks/javadoc/">SDK API Reference
page</a> page, as follows:</p>
 
 <ul>
-  <li>Copy the generated Javadoc into the website repository: <code class="highlighter-rouge">cp
-r ${JAVADOC_ROOT} learn/sdks/javadoc/${VERSION}</code>.</li>
-  <li>Update the Javadoc link on this page to point to the new version.</li>
+  <li>Copy the generated Javadoc into the website repository: <code class="highlighter-rouge">cp
-r ${JAVADOC_ROOT} documentation/sdks/javadoc/${VERSION}</code>.</li>
+  <li>Update the Javadoc link on this page to point to the new version (in <code
class="highlighter-rouge">src/documentation/sdks/javadoc/current.md</code>).</li>
 </ul>
 
 <p>Finally, propose a pull request with these changes. (Don’t merge before finalizing
the release.)</p>


Mime
View raw message