document End of Life policy

Signed-off-by: Nicolas De Loof <[email protected]>

README.md

@@ -4,10 +4,29 @@ Docker Compose
 
 ![Docker Compose](logo.png?raw=true "Docker Compose Logo")
 
-| ** Compose V2 is on his way! :star_struck: ** |
-| --- |
-| We are currently polishing the next generation of Docker Compose, to be released soon... :stopwatch: <br> - Read more on [RC1 announcement](https://www.docker.com/blog/start-dev-environments-locally-compose-v2-rc-1-and-more-in-docker-desktop-3-6/). <br> - Check the [v2 branch](https://github.com/docker/compose/tree/v2) on this repo. |
+** Compose V2 is on its way! :star_struck: **
+---------------------------------------------
 
+We are currently polishing the next generation of Docker Compose, to be released soon... :stopwatch: 
+- Read more on [RC1 announcement](https://www.docker.com/blog/start-dev-environments-locally-compose-v2-rc-1-and-more-in-docker-desktop-3-6/). 
+- Check the [v2 branch](https://github.com/docker/compose/tree/v2) on this repo.
+
+We are working towards providing an easy way to install Compose V2 on Linux. Once this is available, Compose V2 will be marked as generally available, our current target for this is the end of October.
+
+V1 vs V2 transition :hourglass_flowing_sand:
+--------------------------------------------
+
+"Generally Available" will mean:
+- New features and bug fixes will only be considered in the V2 codebase 
+- Users on Mac/Windows will be defaulted into Docker Compose V2, but can still opt out through the UI and the CLI. This means when running `docker-compose` you will actually be running `docker compose`
+- Our current goal is for users on Linux to receive Compose v2 with the latest version of the docker CLI, but is pending some technical discussion. Users will be able to use [compose switch](https://github.com/docker/compose-switch) to enable redirection of `docker-compose` to `docker compose`
+- Docker Compose V1 will continue to be maintained regarding security issues
+- [v2 branch](https://github.com/docker/compose/tree/v2) will become the default one at that time
+
+:lock_with_ink_pen: Depending on the feedback we receive from the community of GA and the adoption on Linux, we will come up with a plan to deprecate v1, but as of right now there is no concrete timeline as we want the transition to be as smooth as possible for all users. It is important to note that we have no plans of removing any aliasing of `docker-compose` to `docker compose`. We want to make it as easy as possible to switch and not break any ones scripts. We will follow up with a blog post in the next few months with more information of an exact timeline of V1 being marked as deprecated and end of support for security issues. We’d love to hear your feedback! You can provide it [here](https://github.com/docker/roadmap/issues/257).
+
+About
+-----
 
 Docker Compose is a tool for running multi-container applications on Docker
 defined using the [Compose file format](https://compose-spec.io).