creating the Velero ROADMAP.md

[michmike]

No description provided.

[skriss]

Added a few comments. My gut also tells me some of these timelines are aggressive - there's a lot of stuff in here. But, we can adjust expectations as we go.

[jonasrosland]

I think this looks great, once the edits requested from @skriss comes in I think this is ready to go.

[skriss]

@ashish-amarnath @carlisia @nrb PTAL!

[carlisia]

Reviewing this in a few.

[carlisia]

This looks OK to me (+ the requested edits). One thing that is not clear is how this work is being distributed amongst the team members (and so if it's balanced), but I assume that has been taken into account.

[skriss]

@ashish-amarnath @nrb last chance to weigh in!

[ashish-amarnath]

LGTM!
Going to let other folks to sign-off too.

[carlisia]

👍

[nrb]

The roadmap's looking pretty good to me!

[stephbman]

worker pods was not included in the roadmap and, after discussing, it looks like worker pods will be a good precursor to get done so that we are more prepared when it is time to do the work on multi-tenancy and self service. I am adding worker pods to the roadmap - @skriss (and team) feel free to weigh in here.

[nrb]

@stephbman I think https://github.com/vmware-tanzu/velero/pull/2548/files#diff-38574c080d4e2eb38c49b86e6588ad98R28 is about worker pods, isn't it?

[stephbman]

@nrb I see it now - I'm not used to reading mark down files (never have until this team) :)

[skriss]

This LGTM and I'll merge it as-is, but I'm still confused on when we're targeting worker pods. This shows it as Dec 2020; but we've talked about doing it for 1.5. Let's clarify this ASAP, and we can follow up with another PR to adjust the roadmap if needed.

[nrb]

@skriss I think Dec 2020 is more realistic given the work involved, and I think that would be ~1.6

[skriss]

Yeah I had mentioned that it might be realistic to target finalizing design for 1.5 and doing execution for 1.6. It sounds like that's probably where we're headed, but still closing the loop on it.