From 4c619ee15cc21bc71fdc8da625b64c38cfdb81aa Mon Sep 17 00:00:00 2001
From: Hannes Mehnert <hannes@mehnert.org>
Date: Tue, 1 Dec 2020 17:42:53 +0100
Subject: [PATCH] changes for 1.0.0

---
 CHANGES.md     | 3 +++
 albatross.opam | 7 +++++++
 2 files changed, 10 insertions(+)

diff --git a/CHANGES.md b/CHANGES.md
index e69de29b..7cfd5e50 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -0,0 +1,3 @@
+# v1.0.0 (2020-12-01)
+
+Initial release
diff --git a/albatross.opam b/albatross.opam
index b9e3b869..86a11760 100644
--- a/albatross.opam
+++ b/albatross.opam
@@ -43,3 +43,10 @@ depexts: [
   ["libnl3" "libnl3-devel"] {os-family = "centos"}
 ]
 synopsis: "Albatross - orchestrate and manage MirageOS unikernels with Solo5"
+description: """
+The goal of albatross is robust deployment of [MirageOS](https://mirage.io)
+unikernels using [Solo5](https://github.com/solo5/solo5). Resources managed
+by albatross are network interfaces of kind `tap`, which are connected to
+already existing bridges, block devices, memory, and CPU. Each unikernel is
+pinned (`cpuset` / `taskset`) to a specific core.
+"""
\ No newline at end of file