[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/src/doc/sdk/release-notes.rst

 .. _sdk-release-notes:
 
 #############
 Release Notes
 #############
 
 Chrome/Pepper 35 (31 Mar 2014)
 ==============================
 
 PNaCl
@@ skipping 83 matching lines @@
 PNaCl (15 May 2013)
 ===================
 
 * Portable Native Client (PNaCl) is currently available for developer preview
   in Chrome 29 or higher.
 * To produce a PNaCl executable (.pexe) file, you must use the pnacl toolchain
   in the current ``pepper_canary`` bundle. Chrome 29 does not support .pexe
   files produced by earlier versions of the pnacl toolchain (that is,
   executables compiled with the ``pepper_28`` bundle or earlier).
 * To run an application with a PNaCl module, you must launch Chrome 29 with the
-  ``--enable-pnacl`` flag (for `packaged apps
-  <http://developer.chrome.com/apps/about_apps.html>`_), or the
+  ``--enable-pnacl`` flag (for `packaged apps </apps/about_apps>`_), or the
   ``--enable-nacl`` flag (for other apps).
 * When you launch Chrome with the ``--enable-pnacl`` flag, Chrome loads a PNaCl
   translator in the background. Wait about a minute after you launch Chrome and
   check `chrome://nacl <chrome://nacl>`_ to verify that the translator loaded.
 * PNaCl translators are currently available for 32-bit x86, 64-bit x86, and ARM
   architectures.
 * PNaCl applications must use the newlib C library (glibc and dynamic linking
   are not supported yet).
 * The intermediate representation (IR) format may change prior to the release
   of PNaCl. If so, you will need to recompile your application with the pnacl
@@ skipping 138 matching lines @@
 * The simple web server included in the SDK, ``httpd.py``, has been moved from
   the ``examples/`` directory to the ``tools/`` directory. On Windows, you can
   run ``httpd.cmd`` (in the ``examples/`` directory) to start the server.
 
 PPAPI
 -----
 
 Pepper 25 includes two new APIs:
 
 * The `Console API
-  <https://developers.google.com/native-client/dev/pepperc/struct_p_p_b___console__1__0>`_
-  lets your module log messages to the JavaScript console in the Chrome browser.
+  </native-client/pepper_stable/c/struct_p_p_b___console__1__0>`_ lets your
+  module log messages to the JavaScript console in the Chrome browser.
 * The `MessageLoop
-  <https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_message_loop>`_
-  API lets your module make PPAPI calls on a background thread.  Once you've
-  created a message loop resource, attached it to a thread, and run it, you can
-  post work to the thread, including completion callbacks for asynchronous
-  operations. For a C++ example of how to use the MessageLoop API,
-  see ``pepper_25/include/ppapi/utility/threading/simple_thread.h``. Note that
-  you cannot make asynchronous PPAPI calls on a background thread without
-  creating and using a message loop.
+  </native-client/pepper_stable/cpp/classpp_1_1_message_loop>`_ API lets your
+  module make PPAPI calls on a background thread.  Once you've created a
+  message loop resource, attached it to a thread, and run it, you can post work
+  to the thread, including completion callbacks for asynchronous operations.
+  For a C++ example of how to use the MessageLoop API, see
+  ``pepper_25/include/ppapi/utility/threading/simple_thread.h``. Note that you
+  cannot make asynchronous PPAPI calls on a background thread without creating
+  and using a message loop.
 
 Libraries
 ---------
 
 The SDK includes two new libraries:
 
 * The **nacl_mounts** library provides a virtual file system that your module
   can "mount" in a given directory tree. The file system can be one of several
   types:
 
@@ skipping 95 matching lines @@
   builds both a debug and a release version.
 * The example Makefiles use dependency (.d) files to enable incremental builds.
 * The pong example has been cleaned up and modified to run more smoothly. The
   drawing function is now set up as the Flush() callback, which allows 2D
   drawing to occur as quickly as possible.
 
 PPAPI
 -----
 
 * When creating a 3D rendering context, the `attribute list
-  <https://developers.google.com/native-client/dev/pepperc/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8>`_
+  </native-client/pepper_stable/c/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8>`_
   for the context can specify whether to prefer low power or performance for
   the GPU. Contexts with a low power preference may be created on an integrated
   GPU; contexts with a performance preference may be created on a discrete GPU.
 
 Windows SDK
 -----------
 
 * The Windows SDK includes the pthreads-win32 library to assist in porting from
   win32 code. You can use this library when developing your module as a Pepper
   plug-in (.dll). See pepper_24/include/win/pthread.h and
   pepper_24/src/pthread/README for additional information.
 * The update utility naclsdk.bat works when it is run from a path with spaces.
 
 Pepper 23 (15 October 2012)
 ===========================
 
 The Pepper 23 bundle includes support for the nacl-gdb debugger on Mac and
 32-bit Windows, resources to enable hosted development on Linux, and changes to
 make the SDK examples compliant with version 2 of the Chrome Web Store manifest
 file format.
 
 Tools
 -----
 
-* The `nacl-gdb debugger
-  <https://developers.google.com/native-client/pepper23/devguide/devcycle/debugging#gdb>`_
-  now works on all systems (Mac, Windows, and Linux).
+* The :ref:`nacl-gdb debugger <using_gdb>` now works on all systems (Mac,
+  Windows, and Linux).
 
 * The output of the SDK update utility has been simplified. When you run the
   command ``naclsdk list``, the utility displays one line for each available
   bundle, annotated with an "``I``" if the bundle is already installed on your
   system, and a "``*``" if the bundle has an update available. To see full
   information about a bundle, use the command ``naclsdk info <bundle>`` (for
   example, ``naclsdk info pepper_28``).
 
 Linux SDK
 ---------
@@ skipping 36 matching lines @@
     :ref:`local server <web_server>` prior to running this command.
 
 Examples
 --------
 
 * On Linux and Windows systems, most of the examples now build with three
   toolchains: the Native Client glibc and newlib toolchains, and the native
   toolchain on the host system. Modules built with the native toolchain on the
   host system can only run as Pepper plugins.
 * All examples in the SDK now comply with version 2 of the Chrome Web Store
-  `manifest file format
-  <http://developer.chrome.com/extensions/manifest.html>`_. By default,
+  `manifest file format </extensions/manifest>`_. By default,
   applications that use version 2 of the manifest file format apply a strict
-  `content security policy
-  <http://developer.chrome.com/extensions/contentSecurityPolicy.html>`_, which
+  `content security policy </extensions/contentSecurityPolicy>`_, which
   includes a restriction against inline JavaScript. This restriction prohibits
   both inline ``<script>`` blocks and inline event handlers (e.g., ``<button
-  onclick="...">``).  See `Manifest Version
-  <http://developer.chrome.com/extensions/manifestVersion.html>`_ for a list of
-  changes between version 1 and version 2 of the manifest file format, and a
-  support schedule for applications that use version 1.
+  onclick="...">``).  See `Manifest Version </extensions/manifestVersion>`_ for
+  a list of changes between version 1 and version 2 of the manifest file
+  format, and a support schedule for applications that use version 1.
 
 PPAPI
 -----
 
 * `PP_InputEvent_Modifier
-  <https://developers.google.com/native-client/pepper23/pepperc/group___enums#ga21b811ac0484a214a8751aa3e1c959d9>`_
+  </native-client/pepper_stable/c/group___enums#ga21b811ac0484a214a8751aa3e1c959d9>`_
   has two new enum values (_ISLEFT and _ISRIGHT).
 * The memory leak in the `WebSocket
-  <https://developers.google.com/native-client/pepper23/pepperc/struct_p_p_b___web_socket__1__0>`_
-  API has been fixed.
+  </native-client/pepper_stable/c/struct_p_p_b___web_socket__1__0>`_ API has
+  been fixed.
 
 Pepper 22 (22 August 2012)
 ==========================
 
 The Pepper 22 bundle includes a **command-line debugger**, resources to enable
 **hosted development on Windows**, and changes to the example Makefiles (each
 example now builds both a debug and a release version).
 
 Tools
 -----
@@ skipping 71 matching lines @@
   in each example's web page, attaches event listeners to monitor the loading
   of the module, and implements handleMessage() to respond to messages sent
   from the NaCl module to the JavaScript side of the application
 
 PPAPI
 -----
 
 * The ``CompletionCallbackFactory`` class template now takes a thread traits
   class as its second parameter. For details see the `CompletionCallbackFactory
   class template reference
-  <https://developers.google.com/native-client/pepper22/peppercpp/classpp_1_1_completion_callback_factory#details>`_.
+  </native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory#details>`_.
 
 .. TODO: Port release notes for older releases