release note for v1.0.0

Signed-off-by: Wang Xu <[email protected]>

Author: gnawux

Diff for: release_notes/latest.md

@@ -1,27 +1,18 @@
-# Version 0.8.1 (2017-05-10)
-
-Bug fix:
-
-- Enable vSock, a communication channel between host and guest.
-- Kubernetes CRI compatibility issues.
-- Container IO stream issues.
-- Fixed the Xen build.
-
-The detail of the issues addressed in 0.8.1 could be found [here][milestone-0.8.1]
-
-# Version 0.8 (2017-03-20)
-
-In this release, several significant updates are introduced, such as **Kubernetes Container Runtime Interface (CRI)** support, **OCI images spec** support:
-
-- Feature: Kubernetes CRI support.
-- Feature: OCI Image Spec support (`hyperctl save -o nginx.tar -f oci `).
-- Interfaces: better GRPC API support.
-- Arch: support ARM64 CPUs with GIC version3, e.g. Cavium ThunderX 64-core CPU.
-- Enhancement: move all the Pod level logic to hyperd, and runV only maintains the sandbox and containers.
-- Enhancement: simplify the model and state machine -- one Pod is one VM.
-- Enhancement: allow add/remove containers to/from a Pod/sandbox.
-- Enhancement: do not stop sandbox without an explicit stop command even if the last container is stopped (To be compatible to Kubernetes CRI).
-
-And many other improvements and updates.
-
-[milestone-0.8.1]:https://github.com/hyperhq/hyperd/milestone/4?closed=1
+# Version 1.0 (2017-09-28)
+
+In release v1.0.0 of HyperContainer, we introduced several significant updates and fixed many bugs to make runV production ready. The featured updates include:
+
+- runV Compatibility:
+  - compatible with the most recent [1.0 of OCI runtime specification](https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0);
+  - compatible with the [latest CNCF containerd](https://github.com/containerd/containerd);
+  - compatible with the latest Docker (17.06.1-ee and later).
+- New hypervisor architectures support:
+  - *xenpv* driver, with the latest Xen 4.9, we could launch runV with very minimal performance penalty (<5 % in most scenarios) on instance of Google GCE and other IaaS platform;
+  - *kvmtool* driver brings the offical ARM support to runV.
+- Feature update:
+  - Pod level portmappings: allow configure port mappings in pod level, and dynamic update port mapping rules;  
+  - Read-only rootfs: allows runV to launch with read-only rootfs;
+  - support vhostuser network card for *qemu* driver, which enables the low latency network for scenarios such as NFV.
+- Many other feature or test improvements, and many bug fix.
+
+Thanks the contribution from Huawei, ZJU, ARM, Intel, Alibaba, and other individuals.

Diff for: release_notes/v1.0.md

@@ -0,0 +1,18 @@
+# Version 1.0 (2017-09-28)
+
+In release v1.0.0 of HyperContainer, we introduced several significant updates and fixed many bugs to make runV production ready. The featured updates include:
+
+- runV Compatibility:
+  - compatible with the most recent [1.0 of OCI runtime specification](https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0);
+  - compatible with the [latest CNCF containerd](https://github.com/containerd/containerd);
+  - compatible with the latest Docker (17.06.1-ee and later).
+- New hypervisor architectures support:
+  - *xenpv* driver, with the latest Xen 4.9, we could launch runV with very minimal performance penalty (<5 % in most scenarios) on instance of Google GCE and other IaaS platform;
+  - *kvmtool* driver brings the offical ARM support to runV.
+- Feature update:
+  - Pod level portmappings: allow configure port mappings in pod level, and dynamic update port mapping rules;  
+  - Read-only rootfs: allows runV to launch with read-only rootfs;
+  - support vhostuser network card for *qemu* driver, which enables the low latency network for scenarios such as NFV.
+- Many other feature or test improvements, and many bug fix.
+
+Thanks the contribution from Huawei, ZJU, ARM, Intel, Alibaba, and other individuals.