mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-06-22 05:28:25 +00:00
docs: update the docs project url from kata 1.x to 2.x
changed the document project url in the using-vpp-and-kata.md and runtime experimental README.md files. Fixes: #2418 Signed-off-by: wangyongchao.bj <wangyongchao.bj@inspur.com>
This commit is contained in:
parent
e1e6827a2c
commit
99ab91df3d
@ -12,7 +12,7 @@ For more information about VPP visit their [wiki](https://wiki.fd.io/view/VPP).
|
|||||||
|
|
||||||
## Install and configure Kata Containers
|
## Install and configure Kata Containers
|
||||||
|
|
||||||
Follow the [Kata Containers setup instructions](https://github.com/kata-containers/documentation/wiki/Developer-Guide).
|
Follow the [Kata Containers setup instructions](../Developer-Guide.md).
|
||||||
|
|
||||||
In order to make use of VHOST-USER based interfaces, the container needs to be backed
|
In order to make use of VHOST-USER based interfaces, the container needs to be backed
|
||||||
by huge pages. `HugePages` support is required for the large memory pool allocation used for
|
by huge pages. `HugePages` support is required for the large memory pool allocation used for
|
||||||
|
@ -56,7 +56,7 @@ That depends.
|
|||||||
For the feature that breaks backward compatibility, we usually land it as formal feature in a major version bump(x in x.y.z, e.g. 2.0.0).
|
For the feature that breaks backward compatibility, we usually land it as formal feature in a major version bump(x in x.y.z, e.g. 2.0.0).
|
||||||
But for a new feature who becomes stable and ready, we can release it formally in any minor version bump.
|
But for a new feature who becomes stable and ready, we can release it formally in any minor version bump.
|
||||||
|
|
||||||
Check Kata Container [versioning rules](https://github.com/kata-containers/documentation/blob/c556f1853f2e3df69d336de01ad4bb38e64ecc1b/Releases.md#versioning).
|
Check Kata Container [versioning rules](../../../../docs/Stable-Branch-Strategy.md#Versioning).
|
||||||
|
|
||||||
The experimental feature should state clearly in documentation the rationale for it to be experimental,
|
The experimental feature should state clearly in documentation the rationale for it to be experimental,
|
||||||
and when it is expected to be non-experimental,
|
and when it is expected to be non-experimental,
|
||||||
|
Loading…
Reference in New Issue
Block a user