Move 'Versioning' topic from overview to download page.

Move 'Versioning' topic from overview to download page.

BUG=none
R= mkearney@chromium.org, smain@chromium.org
TEST=none
NOTRY=true
(documentation only change)

Committed: https://crrev.com/666ae732a0617c25ea7f10660fc39cbfedfba80a
Cr-Commit-Position: refs/heads/master@{#296075}

[jpmedley, 2014-09-05 21:27:03]

Please review.

[binji, 2014-09-09 17:35:15]

binji@chromium.org changed reviewers:
+ binji@chromium.org

[binji, 2014-09-09 17:35:15]

Seems OK to me, but why are you moving it to the download page?

[jpmedley, 2014-09-09 18:07:29]

On 2014/09/09 17:35:15, binji wrote:
> Seems OK to me, but why are you moving it to the download page?

I think it's more relevant there. The overview is all conceptual stuff. While
you can argue that versioning is conceptual, it seems more like something you'd
need to know when your downloading.

[jpmedley, 2014-09-09 18:08:18]

On 2014/09/09 18:07:29, jmedley wrote:
> On 2014/09/09 17:35:15, binji wrote:
> > Seems OK to me, but why are you moving it to the download page?
> 
> I think it's more relevant there. The overview is all conceptual stuff. While
> you can argue that versioning is conceptual, it seems more like something
you'd
> need to know when your downloading.
Oops
when you're downloading.

[jpmedley, 2014-09-22 21:58:46]

jmedley@chromium.org changed reviewers:
+ jfb@chromium.org
- binji@chromium.org

[jpmedley, 2014-09-22 21:58:46]

I just noticed that this went to the wrong guy originally. The question to ask
yourself is not, "where does this section go"? The question is, "when is this
section needed"/

[JF, 2014-09-22 22:11:55]

lgtm

[jpmedley, 2014-09-22 22:13:21]

The CQ bit was checked by jmedley@chromium.org

[commit-bot: I haz the power, 2014-09-22 22:15:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/536823004/1

[commit-bot: I haz the power, 2014-09-22 22:18:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-22 22:18:10]

Failed to apply patch for native_client_sdk/doc_generated/overview.html:
While running git apply --index -p1;
  error: patch failed: native_client_sdk/doc_generated/overview.html:19
  error: native_client_sdk/doc_generated/overview.html: patch does not apply

Patch:       native_client_sdk/doc_generated/overview.html
Index: native_client_sdk/doc_generated/overview.html
diff --git a/native_client_sdk/doc_generated/overview.html
b/native_client_sdk/doc_generated/overview.html
index
7886ddcbc6878fac0790a6502687a7e6428cebdb..390bc4d0ad59448af49142f42dff4651df008e18
100644
--- a/native_client_sdk/doc_generated/overview.html
+++ b/native_client_sdk/doc_generated/overview.html
@@ -19,8 +19,7 @@
 <li><a class="reference internal" href="#pepper-plugin-api" id="id10">Pepper
Plugin API</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#versioning"
id="id11">Versioning</a></li>
-<li><a class="reference internal" href="#where-to-start" id="id12">Where to
start</a></li>
+<li><a class="reference internal" href="#where-to-start" id="id11">Where to
start</a></li>
 </ul>
 
 </div><h2 id="introduction">Introduction</h2>
@@ -204,15 +203,6 @@ capabilities, including:</p>
 <p>Pepper includes both a C API and a C++ API. The C++ API is a set of bindings
 written on top of the C API. For additional information about Pepper, see
 <a class="reference external"
href="http://code.google.com/p/ppapi/wiki/Concepts">Pepper Concepts</a>.</p>
-<h2 id="versioning">Versioning</h2>
-<p>Chrome is released on a six week cycle, and developer versions of Chrome are
-pushed to the public beta channel three weeks before each release. As with any
-software, each release of Chrome may include changes to Native Client and the
-Pepper interfaces that may require modification to existing applications.
-However, modules compiled for one version of Pepper/Chrome should work with
-subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
-Pepper APIs to help developers make adjustments to API changes and take
-advantage of new features: <a class="reference external"
href="/native-client/pepper_stable">stable</a>, <a class="reference external"
href="/native-client/pepper_beta">beta</a> and <a class="reference external"
href="/native-client/pepper_dev">dev</a>.</p>
 <h2 id="where-to-start">Where to start</h2>
 <p>The <a class="reference internal"
href="/native-client/quick-start.html"><em>Quick Start</em></a> document
provides links to downloads and
 documentation that should help you get started with developing and distributing

[jpmedley, 2014-09-22 22:35:43]

The CQ bit was checked by jmedley@chromium.org

[commit-bot: I haz the power, 2014-09-22 22:36:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/536823004/20001

[commit-bot: I haz the power, 2014-09-22 22:37:28]

Committed patchset #2 (id:20001) as bb9b28e1997dcd5e9631fb4564ad5e462b27b506

[commit-bot: I haz the power, 2014-09-22 22:38:02]

Patchset 2 (id:??) landed as
https://crrev.com/666ae732a0617c25ea7f10660fc39cbfedfba80a
Cr-Commit-Position: refs/heads/master@{#296075}