Propose talk about Gerrit migrations
Change-Id: I02157bd30a1bf9ca6d0ea0f732f6b1a5189ad275
diff --git a/schedule-usa.md b/schedule-usa.md
index 7a8363f..811cf2f 100644
--- a/schedule-usa.md
+++ b/schedule-usa.md
@@ -27,7 +27,7 @@
| 11:45 | Gerrit goes multi-site |
| 12:45 | Lunch & Networking |
| 14:00 | [JGit (concrete topic to be decided)](sessions/jgit.md)
-| 15:00 | << Gerrit case study - slot available >> |
+| 15:00 | [Gerrit upgrades, step-by-step](sessions/gerrit-upgrades-step-by-step.md) |
| 16:00 | Break & Networking |
| 16:30 | Lightning talks <br/>- [Show me your dashboard - 10'](lightning-talks/show-me-your-dashboards.md)
| 17:30 | End of Day 1 |
diff --git a/sessions/gerrit-upgrades-step-by-step.md b/sessions/gerrit-upgrades-step-by-step.md
new file mode 100644
index 0000000..50a1bd0
--- /dev/null
+++ b/sessions/gerrit-upgrades-step-by-step.md
@@ -0,0 +1,15 @@
+# Gerrit upgrades, step-by-step
+
+Upgrading is always a pain, no matter big or small.
+Gerrit 3.1 is planned to be released on November 2019 and, sooner or later,
+all the current older versions would need to be migrated to a modern 3.x release.
+
+This talk is to demystify the fears of upgrading and covering step-by-step,
+all the DOs and DONTs of the process, from a real-life example of upgrading
+in GerritHub.io and with large Gerrit Enterprise setups.
+
+Join me for seeing in practice how to make your upgrade path smoother and less
+painful. See how the upgrade can be also achieved without having to stop the
+incoming traffic to your Gerrit servers.
+
+*[Luca Milanesio, Gerrit Maintainer / GerritForge Ltd](../speakers.md#lmilanesio)*
