Doc server manifest page generation

chrome/common/extensions/docs/templates/articles/manifest/version.html

Index: chrome/common/extensions/docs/templates/articles/manifest/version.html
diff --git a/chrome/common/extensions/docs/templates/articles/manifest/version.html b/chrome/common/extensions/docs/templates/articles/manifest/version.html
new file mode 100644
index 0000000000000000000000000000000000000000..2b7406bd2014cb83f47adc116e160f0ecbcc243c
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/articles/manifest/version.html
@@ -0,0 +1,48 @@
+<h1 id="version">Manifest - Version</h1>
+
+<p>
+One to four dot-separated integers
+identifying the version of this extension.
+A couple of rules apply to the integers:
+they must be between 0 and 65535, inclusive,
+and non-zero integers can't start with 0.
+For example, 99999 and 032 are both invalid.
+</p>
+
+<p>
+Here are some examples of valid versions:
+</p>
+
+<ul>
+  <li> <code>"version": "1"</code> </li>
+  <li> <code>"version": "1.0"</code> </li>
+  <li> <code>"version": "2.10.2"</code> </li>
+  <li> <code>"version": "3.1.2.4567"</code> </li>
+</ul>
+
+<p>
+The autoupdate system compares versions
+to determine whether an installed extension
+needs to be updated.
+If the published extension has a newer version string
+than the installed extension,
+then the extension is automatically updated.
+</p>
+
+<p>
+The comparison starts with the leftmost integers.
+If those integers are equal,
+the integers to the right are compared,
+and so on.
+For example, 1.2.0 is a newer version than 1.1.9.9999.
+</p>
+
+<p>
+A missing integer is equal to zero.
+For example, 1.1.9.9999 is newer than 1.1.
+</p>
+
+<p>
+For more information, see
+<a href="http://developer.chrome.com/extensions/autoupdate.html">Autoupdating</a>.
+</p>