Move versioning.md to design/ -- not user-focused.

This commit is contained in:
Eric Tune 2015-07-13 16:25:16 -07:00
parent c6161824db
commit e463723f03
2 changed files with 2 additions and 2 deletions

View File

@ -40,7 +40,7 @@ Fine-grain resource evolution alone makes it difficult to eliminate fields or re
Distinct API versions present more clear, consistent views of system resources and behavior than intermingled, independently evolved resources. They also provide a more straightforward mechanism for controlling access to end-of-lifed and/or experimental APIs.
The [API and release versioning proposal](versioning.md) describes the current thinking on the API version evolution process.
The [API and release versioning proposal](design/versioning.md) describes the current thinking on the API version evolution process.
## v1beta1, v1beta2, and v1beta3 are deprecated; please move to v1 ASAP

View File

@ -60,5 +60,5 @@ There is a separate question of how to track the capabilities of a kubelet to fa
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/versioning.md?pixel)]()
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/versioning.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->