Merge pull request #210 from michelleN/v0.6.0

chore(*): prepare spec for v0.6.0 release

Author: Michelle Noorali

README.md

@@ -15,16 +15,16 @@ interoperability, and covers the most common service mesh capabilities.
 
 The following documents are available:
 
-|                               |         Latest Release             |    Working Draft                           |
-| :---------------------------- | :--------------------------------: | :----------------------------------------: |
+|                               |         Latest Release             |  
+| :---------------------------- | :--------------------------------: |
 | **Core Specification:**       |
-| SMI Specification             |  [v0.5.0](/SPEC_LATEST_STABLE.md) |  [v0.6.0-WD](/SPEC_WORKING_DRAFT.md)  |
+| SMI Specification             |  [v0.6.0](/SPEC_LATEST_STABLE.md) |
 |                               |
 | **Specification Components**  |
-| Traffic Access Control  |  [v1alpha2](/apis/traffic-access/v1alpha2/traffic-access.md)  |  [v1alpha3-WD](/apis/traffic-access/traffic-access-WD.md)          |
-| Traffic Metrics   |  [v1alpha1](/apis/traffic-metrics/v1alpha1/traffic-metrics.md)  |  [v1alpha2-WD](/apis/traffic-metrics/traffic-metrics-WD.md)          |
-| Traffic Specs  |  [v1alpha3](/apis/traffic-specs/v1alpha3/traffic-specs.md)  |  [v1alpha4-WD](/apis/traffic-specs/traffic-specs-WD.md)          |
-| Traffic Split  |  [v1alpha3](/apis/traffic-split/v1alpha3/traffic-split.md) |  [v1alpha4-WD](/apis/traffic-split/traffic-split-WD.md)          |
+| Traffic Access Control  |  [v1alpha3](/apis/traffic-access/v1alpha3/traffic-access.md)  |
+| Traffic Metrics   |  [v1alpha1](/apis/traffic-metrics/v1alpha1/traffic-metrics.md)  |
+| Traffic Specs  |  [v1alpha4](/apis/traffic-specs/v1alpha4/traffic-specs.md)  |
+| Traffic Split  |  [v1alpha4](/apis/traffic-split/v1alpha4/traffic-split.md) |
 
 ## Ecosystem
 

SPEC_LATEST_STABLE.md

@@ -2,7 +2,7 @@
 
 ## Version
 
-This is SMI **spec** version **v0.5.0**.
+This is SMI **spec** version **v0.6.0**.
 Learn more about versioning [below](#versioning).
 
 ## Table of Contents
@@ -80,7 +80,7 @@ drafts can be found under the [apis/ directory](apis/)_
 
 Apply policies like identity and transport encryption across services.
 
-The [Traffic Access Control](apis/traffic-access/v1alpha2/traffic-access.md) API
+The [Traffic Access Control](apis/traffic-access/v1alpha3/traffic-access.md) API
 describes a resource to configure access to specific pods and routes based
 on the identity of a client for locking down applications to only allowed
 users and services.
@@ -89,15 +89,15 @@ users and services.
 
 Shift traffic between different services.
 
-The [Traffic Split](apis/traffic-split/v1alpha3/traffic-split.md) API describes
+The [Traffic Split](apis/traffic-split/v1alpha4/traffic-split.md) API describes
 a resource to incrementally direct percentages of traffic between various services
 to assist in building out canary rollouts.
 
 ### Traffic Specs
 
 Describe traffic on a per-protocol basis.
 
-The [Traffic Specs](apis/traffic-specs/v1alpha3/traffic-specs.md) API describes
+The [Traffic Specs](apis/traffic-specs/v1alpha4/traffic-specs.md) API describes
 a set of resources to define how traffic looks on a per-protocol basis. These
 resources work in concert with access control and other types of policy to manage
 traffic at a protocol level.

SPEC_WORKING_DRAFT.md

@@ -2,9 +2,9 @@
 
 **API Group:** access.smi-spec.io
 
-**API Version:** v1alpha3-WD
+**API Version:** v1alpha3
 
-**Compatible with:** specs.smi-spec.io/v1alpha4-WD
+**Compatible with:** specs.smi-spec.io/v1alpha4
 
 ## Specification
 
@@ -19,7 +19,7 @@ See [tradeoffs](#tradeoffs) for a longer discussion about why.
 
 A `TrafficTarget` associates a set of traffic definitions (rules) with a
 service identity which is allocated to a group of pods.  Access is controlled
-via referenced [TrafficSpecs](/apis/traffic-specs/v1alpha3/traffic-specs.md)
+via referenced [TrafficSpecs](/apis/traffic-specs/v1alpha4/traffic-specs.md)
 and by a list of source service identities.  If a pod which holds the reference
 service identity makes a call to the destination on one of the defined routes
 then access will be allowed. Any pod which attempts to connect and is not in
@@ -31,7 +31,7 @@ Access is controlled based on service identity, at present the method of
 assigning service identity is using Kubernetes service accounts, provision for
 other identity mechanisms will be handled by the spec at a later date.
 
-Rules are [traffic specs](/apis/traffic-specs/v1alpha3/traffic-specs.md) that
+Rules are [traffic specs](/apis/traffic-specs/v1alpha4/traffic-specs.md) that
 define what traffic for specific protocols would look like. The kind can be
 different depending on what traffic a target is serving. In the following
 examples, `HTTPRouteGroup` is used for applications serving HTTP based traffic.