Remove references to Alpha and introcuce global version identifier.

_data/istio.yml

@@ -0,0 +1 @@
+version: 0.1

_docs/concepts/policy-and-control/mixer.md

@@ -35,16 +35,16 @@ Mixer provides three core features:
 - **Precondition Checking**. Enables callers to verify a number of preconditions before responding to an incoming request from a service consumer. 
 Preconditions can include whether the service consumer is properly authenticated, is on the service's whitelist, passes ACL checks, and more.
 
-- **Telemetry Reporting**. Enables services to report logging and monitoring. In the future, it will also enable tracing and billing
-streams intended for both the service operator as well as for service consumers.
-
 - **Quota Management**. Enables services to allocate and free quota on a number of dimensions, Quotas are used as a relatively simple resource
 management tool to provide some fairness between service consumers when contending for limited resources. Rate limits are
 examples of quotas.
 
+- **Telemetry Reporting**. Enables services to report logging and monitoring. In the future, it will also enable tracing and billing
+streams intended for both the service operator as well as for service consumers.
+
 These mechanisms are applied based on a set of [attributes](./attributes.html) that are
 materialized for every request into Mixer. Within Istio, Envoy depends heavily on Mixer. Services running within the mesh
-can also use Mixer to report telemetry or manage quotas. (Note: as of Istio Alpha, only Envoy can call Mixer.)
+can also use Mixer to report telemetry or manage quotas. (Note: as of Istio {{ site.data.istio.version }}, only Envoy can call Mixer.)
 
 ## Adapters
 
@@ -52,6 +52,7 @@ Mixer is a highly modular and extensible component. One of it's key functions is
 away the details of different policy and telemetry backend systems, allowing Envoy and Istio-based
 services to be agnostic of those backends, which keeps them portable.
 
+
 Mixer's flexibility in dealing with different infrastructure backends is achieved by having a general-purpose
 plug-in model. Individual plug-ins are known as *adapters* and they allow
 Mixer to interface to different infrastructure backends that deliver core functionality, such as logging, monitoring, quotas, ACL

_docs/tasks/installing-istio.md

@@ -26,7 +26,7 @@ This page shows how to install and configure Istio in a Kubernetes cluster.
 
 ## Installing on an existing cluster
 
-For the Alpha release, Istio must be installed in the same Kubernetes namespace as the applications. Instructions below will deploy Istio in the
+For the {{ site.data.istio.version }} release, Istio must be installed in the same Kubernetes namespace as the applications. Instructions below will deploy Istio in the
 default namespace. They can be modified for deployment in a different namespace.
 
 1. Download and extract the [istio installation files](https://raw.githubusercontent.com/istio/istio/master/releases/istio-0.1.tar.gz), or
@@ -41,6 +41,7 @@ clone Istio's [GitHub](https://github.com/istio/istio) repository:
    ```bash
    cd install/kubernetes
    ```
+   ```
 
 3. Determine if your cluster has [RBAC enabled](https://kubernetes.io/docs/admin/authorization/rbac/) by running this command:
 

_includes/footer.html

@@ -50,6 +50,7 @@
         <div class="row">
             <p class="description small text-center">
                 Copyright &copy; 2017 Istio Authors<br>
+                Istio Version 0.1<br>
                 This site was built on {{site.time | date_to_string | split: ' ' | join: '-'}}
             </p>
         </div>

faq/index.md

@@ -47,7 +47,8 @@ Istio uses the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0.
 
 #### What deployment environments are supported?
 
-Istio is designed and built to be platform-independent. For our initial Alpha release, however, Istio only supports environments running Kubernetes v1.5 or 
+Istio is designed and built to be platform-independent. For our {{ site.data.istio.version }} release, however, Istio only supports environments running 
+Kubernetes v1.5 or 
 greater. 
 
 #### How can I contribute?
@@ -86,12 +87,13 @@ Our [user mailing list](https://groups.google.com/forum/#!forum/istio-users) is
 Additionally, we provide [Reference Guides]({{home}}/docs/reference/) for all of the Istio components. These can be helpful when troubleshooting issues with 
 configuration, etc.
 
-#### What does the Alpha release cover?
+#### What does the {{ site.data.istio.version }} release cover?
 
-Istio's Alpha release provides an early preview of the intended functionality and user experience of our service mesh. We are hoping to solicit 
+Istio's {{ site.data.istio.version }} release provides an early preview of the intended functionality and user experience of our service mesh. We are hoping to 
+solicit 
 early feedback on direction and design decisions.
 
-The Alpha release includes the following features:
+The {{ site.data.istio.version }} release includes the following features:
 
 *   Simple command-line installation into a Kubernetes cluster
 
@@ -127,11 +129,13 @@ Kubernetes secret security, from secret encryption to node-level access control.
 
 #### What kind of traffic does Istio Auth support?
 
-For Alpha, we only support HTTP traffic. And we are actively working on supporting more kinds of traffic like SQL, etc.
+For {{ site.data.istio.version }}, we only support HTTP traffic. And we are actively working on supporting more kinds of traffic like SQL, etc.
 
 #### What is Istio's roadmap?
 
-Istio's initial Alpha release will be in May of 2017. The Alpha release is to get early feedback and provide a glimpse into what we're planning.
+Istio's initial {{ site.data.istio.version }} release will be in May of 2017. The {{ site.data.istio.version }} release is to get early feedback and provide a glimpse into 
+what we're 
+planning.
 
 We are planning a Beta release later in 2017 which will be suitable for use in production environments.