Reconsider scope of v3
At the current stale state of development, I think we can shave off ideas for v3, release it, and enhance later on. We're close to being 2 years since it's inception, yet none of the code we wrote for it reached production, that can be an absolute killer for motivation (it sure is being one for me).
This is mostly a draft for the future milestones (splitting v3 into v3.1 and *maybe v4), so it might not be complete. If an issue is not being cited here, assume it's on the "Must haves for v3" category.
Must haves for v3: #141 (closed), #151 (closed), #140, #139, #125 (closed), #58, #165 (closed)
Drop from v3, keep for the future: #127, #168, #142
Must decide w/ FE: #156 (closed)
Should go on a v3.1 (as they don't change API, and are backend enhancements, I think it is justified to leave them there): #154 (closed), #166
Must decide w/ @Mstrodl (if v3 or v4, as API breaking change): #145
Must decide w/ @slice (if v3 or v4, as API breaking change): #143
Must decide w/ backend: #112