[libvirt-dockerfiles PATCH] README: Update to reflect repository status

[Andrea Bolognani]

The contents of this repository are no longer used, so briefly
explain why that is the case and point interested people in the
right direction.

Signed-off-by: Andrea Bolognani <abologna at redhat.com>
---
 README.md  | 51 ---------------------------------------------------
 README.rst | 12 ++++++++++++
 2 files changed, 12 insertions(+), 51 deletions(-)
 delete mode 100644 README.md
 create mode 100644 README.rst

diff --git a/README.md b/README.md
deleted file mode 100644
index 3508517..0000000
--- a/README.md
+++ /dev/null
@@ -1,51 +0,0 @@
-Docker-based build environments for libvirt
-===========================================
-
-These images come with all libvirt build dependencies, including
-optional ones, already installed: this makes it possible to run
-something like
-
-    $ docker run \
-      -v $(pwd):/libvirt \
-      -w /libvirt \
-      -it \
-      buildenv-centos-7
-
-from a git clone and start building libvirt right away.
-
-Image availability is influenced by libvirt's
-[platform support policy](https://libvirt.org/platforms.html),
-with the obvious caveat that non-Linux operating systems can't
-be run on top of a Linux kernel and as such are not included.
-
-
-Intended use
-------------
-
-The images are primarily intended for use on
-[Travis CI](https://travis-ci.org/libvirt/libvirt).
-
-The primary CI environment for the libvirt project is hosted on
-[CentOS CI](https://ci.centos.org/view/libvirt/); however, since
-that environment feeds off the `master` branch of the various
-projects, it can only detect issues after the code causing them
-has already been merged.
-
-While testing on Travis CI doesn't cover as many platforms or the
-interactions between as many components, it can be very useful as
-a smoke test of sorts that allows developers to catch mistakes
-before posting patches to the mailing list.
-
-As an alternative, images can be used locally without relying on
-third-party services; in this scenario, the number of platforms
-patches are tested against is only limited by image availability
-and hardware resources.
-
-
-Information about build dependencies
-------------------------------------
-
-The list of build dependencies for libvirt (as well as many
-other virtualization-related projects) is taken from the
-[libvirt-ci](https://gitlab.com/libvirt/libvirt-ci) repository,
-which also contains the tooling used to generate Dockerfiles.
diff --git a/README.rst b/README.rst
new file mode 100644
index 0000000..ecdabcf
--- /dev/null
+++ b/README.rst
@@ -0,0 +1,12 @@
+===================================
+!!! This repository is obsolete !!!
+===================================
+
+Container images are now generated as part of the GitLab CI pipeline
+for the respective projects and hosted on the GitLab container
+registry instead of being generated and hosted on Quay, with builds
+triggered manually using the scripts in this repository; the
+Dockerfiles themselves are also now part of the project's repository
+instead of being centrally managed here.
+
+For more information, look into each project's ``ci/`` directory.
-- 
2.25.4