Propose project roadmap and update status of postmortem action items

Signed-off-by: Marek Siarkowicz <[email protected]>

Documentation/postmortems/v3.5-data-inconsistency.md

@@ -115,18 +115,18 @@ To reflect this action items should have assigned priority:
 * P1 - Important for long term success of the project. Blocks v3.6 release.
 * P2 - Stretch  goals that would be nice to have for v3.6, however should not be blocking.
 
-| Action Item                                                                         | Type     | Priority | Bug                                          |
-|-------------------------------------------------------------------------------------|----------|----------|----------------------------------------------|
-| etcd testing can reproduce historical data inconsistency issues                     | Prevent  | P0       | https://github.com/etcd-io/etcd/issues/14045 |
-| etcd detects data corruption by default                                             | Detect   | P0       | https://github.com/etcd-io/etcd/issues/14039 |
-| etcd testing is high quality, easy to maintain and expand                           | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13637 |
-| etcd apply code should be easy to understand and validate correctness               | Prevent  | P1       |                                              |
-| Critical etcd features are not abandoned when contributors move on                  | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13775 |
-| etcd is continuously qualified with failure injection                               | Prevent  | P1       |                                              |
-| etcd can reliably detect data corruption (hash is linearizable)                     | Detect   | P1       |                                              |
-| etcd checks consistency of snapshots sent between leader and followers              | Detect   | P1       | https://github.com/etcd-io/etcd/issues/13973 |
-| etcd recovery from data inconsistency procedures are documented and tested          | Mitigate | P1       |                                              |
-| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2       | https://github.com/etcd-io/etcd/issues/13839 |
+| Action Item                                                                         | Type     | Priority | Bug                                          | Status |
+|-------------------------------------------------------------------------------------|----------|----------|----------------------------------------------|--------|
+| etcd testing can reproduce historical data inconsistency issues                     | Prevent  | P0       | https://github.com/etcd-io/etcd/issues/14045 | DONE   |
+| etcd detects data corruption by default                                             | Detect   | P0       | https://github.com/etcd-io/etcd/issues/14039 | DONE   |
+| etcd testing is high quality, easy to maintain and expand                           | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13637 |        |
+| etcd apply code should be easy to understand and validate correctness               | Prevent  | P1       |                                              |        |
+| Critical etcd features are not abandoned when contributors move on                  | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13775 | DONE   |
+| etcd is continuously qualified with failure injection                               | Prevent  | P1       | https://github.com/etcd-io/etcd/pull/14911   | DONE   |
+| etcd can reliably detect data corruption (hash is linearizable)                     | Detect   | P1       |                                              |        |
+| etcd checks consistency of snapshots sent between leader and followers              | Detect   | P1       | https://github.com/etcd-io/etcd/issues/13973 | DONE   |
+| etcd recovery from data inconsistency procedures are documented and tested          | Mitigate | P1       |                                              |        |
+| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2       | https://github.com/etcd-io/etcd/issues/13839 |        |
 
 ## Timeline
 

README.md

@@ -136,6 +136,7 @@ Now it's time to dig into the full etcd API and other guides.
 
 - Email: [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev)
 - Slack: [#etcd](https://kubernetes.slack.com/messages/C3HD8ARJ5/details/) channel on Kubernetes ([get an invite](http://slack.kubernetes.io/))
+- [Roadmap](./ROADMAP.md)
 - [Community meetings](#Community-meetings)
 
 ### Community meetings

ROADMAP.md

@@ -0,0 +1,24 @@
+# etcd roadmap
+
+This document defines high level goals for project.
+
+## Milestones
+
+* [P0] Etcd releases are qualified by rigorous robustness testing
+* [P0] Etcd can reliably detect data corruption
+* [P1] Experimental features are graduated or removed
+* [P1] Etcd testing is high quality, easy to maintain and expand
+* [P1] Etcd v2 API and storage is removed and code cleaned up
+* [P1] Etcd supports zero-downtime downgrade
+* [P2] Etcd can automatically recover from data corruption
+
+Each listed milestone should have a corresponding 
+[issue](https://github.com/etcd-io/etcd/issues) or
+[milestone](https://github.com/etcd-io/etcd/milestones) on GitHub. 
+If it doesn't please [let us know](https://github.com/etcd-io/etcd#contact).
+
+### Priorities
+
+* P0 - Critical for reliability of the v3.5 and v3.4 releases. Should be prioritized this over all other work and back-ported.
+* P1 - Important for long term success of the project. Blocks v3.6 release.
+* P2 - Stretch goals that would be nice to have for v3.6, however should not be blocking.