new roadmap for 1.7 (#4048)

Signed-off-by: Eleanor Millman <emillman@vmware.com>

ROADMAP.md

@@ -15,55 +15,33 @@ We work with and rely on community feedback to focus our efforts to improve Vele
 The following table includes the current roadmap for Velero. If you have any questions or would like to contribute to Velero, please attend a [community meeting](https://velero.io/community/) to discuss with our team. If you don't know where to start, we are always looking for contributors that will help us reduce technical, automation, and documentation debt.
 Please take the timelines & dates as proposals and goals. Priorities and requirements change based on community feedback, roadblocks encountered, community contributions, etc. If you depend on a specific item, we encourage you to attend community meetings to get updated status information, or help us deliver that feature by contributing to Velero.
 
-`Last Updated: March 2021`
+`Last Updated: July 2021`
 
-#### 1.7.0 Roadmap
-The release roadmap is split into Core items that are required for the release, desired items that may be removed from the
-release and opportunistic items that will be added to the release if possible.
+#### 1.7.0 Roadmap (to be delivered early fall)
+The release roadmap is split into Core items that are required for the release and desired items that may slip the release.
 
 ##### Core items
+The top priority of 1.7 is to increase the technical health of Velero and be more efficient with Velero developer time by streamlining the release process and automating and expanding the E2E test suite.
 
 |Issue|Description|
 |---|---|
+||Streamline release process|
+||Automate the running of the E2E tests|
+||Convert pre-release manual tests to automated E2E tests|
 |[3493](https://github.com/vmware-tanzu/velero/issues/3493)|[Carvel](https://github.com/vmware-tanzu/velero/issues/3493) based installation (in addition to the existing *velero install* CLI).|
-|[3531](https://github.com/vmware-tanzu/velero/issues/3531)|Test plan for Velero|
 |[675](https://github.com/vmware-tanzu/velero/issues/675)|Velero command to generate debugging information.  Will integrate with [Crashd - Crash Diagnostics](https://github.com/vmware-tanzu/velero/issues/675)|
-|[2066](https://github.com/vmware-tanzu/velero/issues/2066)|CSI Snapshots GA|
-|[3285](https://github.com/vmware-tanzu/velero/issues/3285)|Support Velero plugin versioning|
+|[3285](https://github.com/vmware-tanzu/velero/issues/3285)|Design doc for Velero plugin versioning|
 |[1975](https://github.com/vmware-tanzu/velero/issues/1975)|IPV6 support|
+|[3533](https://github.com/vmware-tanzu/velero/issues/3533)|Upload Progress Monitoring|
+|[3500](https://github.com/vmware-tanzu/velero/issues/3500)|Use distroless containers as a base|
 
 
 
-##### Desired items
+##### Items formerly in 1.7 that will slip due to staffing changes
 |Issue|Description|
 |---|---|
-|[3533](https://github.com/vmware-tanzu/velero/issues/3533)|Upload Progress Monitoring|
-|[2922](https://github.com/vmware-tanzu/velero/issues/2922)|Plugin timeouts|
-|[3500](https://github.com/vmware-tanzu/velero/issues/3500)|Use distroless containers as a base|
-|[3535](https://github.com/vmware-tanzu/velero/issues/3535)|Design doc for multiple cluster support|
 |[3536](https://github.com/vmware-tanzu/velero/issues/3536)|Manifest for backup/restore|
-
-##### Opportunistic items
-|Issue|Description|
-|---|---|
-|Issues TBD|Controller migrations|
-
-#### Long term roadmap items
-|Theme|Description|Timeline|
-|---|---|---|
-|Restic Improvements|Introduce improvements in annotating resources for Restic backup|TBD|
-|Extensibility|Add restore hooks for enhanced recovery scenarios|TBD|
-|CSI|Continue improving the CSI snapshot capabilities and participate in the upstream K8s CSI community|1.7.0 + Long running (dependent on CSI working group)|
-|Backup/Restore|Improvements to long-running copy operations from a performance and reliability standpoint|1.7.0|
-|Quality/Reliability| Enable automated end-to-end testing |1.6.0|
-|UX|Improvements to install and configuration user experience|Dec 2020|
-|Restic Improvements|Improve the use of Restic in Velero and offer stable support|TBD|
-|Perf & Scale|Introduce a scalable model by using a worker pod for each backup/restore operation and improve operations|1.8.0|
-|Backup/Restore|Better backup and restore semantics for certain Kubernetes resources like stateful sets, operators|2.0|
-|Security|Enable the use of custom credential providers|1.6.0|
-|Self-Service & Multitenancy|Reduce friction by enabling developers to backup their namespaces via self-service. Introduce a Velero multi-tenancy model, enabling owners of namespaces to backup and restore within their access scope|TBD|
-|Backup/Restore|Cross availability zone or region backup and restore|TBD|
-|Application Consistency|Offer blueprints for backing up and restoring popular applications|TBD|
-|Backup/Restore|Data only backup and restore|TBD|
-|Backup/Restore|Introduce the ability to overwrite existing objects during a restore|TBD|
-|Backup/Restore|What-if dry run for backup and restore|1.7.0|
+|[2066](https://github.com/vmware-tanzu/velero/issues/2066)|CSI Snapshots GA|
+|[3535](https://github.com/vmware-tanzu/velero/issues/3535)|Design doc for multiple cluster support|
+|[2922](https://github.com/vmware-tanzu/velero/issues/2922)|Plugin timeouts|
+|[3531](https://github.com/vmware-tanzu/velero/issues/3531)|Test plan for Velero|