diff --git a/LATEST_VERSIONS b/LATEST_VERSIONS
new file mode 100644
index 0000000..d64cfd7
--- /dev/null
+++ b/LATEST_VERSIONS
@@ -0,0 +1,8 @@
+# all versions >= 0.9.2~dev should use 0.9.2
+dev 0.9.2
+# all version < 0.9.2~dev should use 0.9.2
+0.9.2~dev 0.9.2
+0.9.0~dev 0.9.1
+0.9.0~dev 0.9.0
+# all version < 0.9.0~dev should use 0.8.0
+0.9.0~dev 0.8.0
diff --git a/README.md b/README.md
index 9eef257..a53b5d1 100644
--- a/README.md
+++ b/README.md
@@ -12,9 +12,13 @@ Versioned files for `drom`
    and `<branch>` is the branch you want to test
 4. Edit the files:
    * `VERSION`: the new version of this branch
-   * `LATEST`: a *stable* version that users are advised to use
    * `DROM_VERSION`: if `drom` must be upgraded to use this version
 5. Push to `master` and remote tag the version
+6. Once the version is tested ok, update `LATEST_VERSIONS`:
+   * `dev` version should point to the new tagged version
+   * the previously `dev` version should be moved to the next line,
+      with the content of its `DROM_VERSION` as corresponding drom
+      version (often with `~dev` to match development versions too)
 
 ## Syntax of skeletons in `projects/` and `packages/`