After the debacle of "Mir 1.0" last year I don't predict what the release will be called if I don't have to.
OK, fair enough.
This is the only pointer I have:
It does need to be updated for Mir changes since then.
I confess I'm finding the upstream/ubports relationship a bit difficult to follow from the existing repo (and not only for mir). There doesn't seem to be a very rigorous maintenance of the boundaries between local patches and upstream.
It would be really, really helpful if there would be a stronger distinction between well-defined master- or major-version branches (whether tracking an upstream or not), versus branches dedicated to specific distro packages.
I have had some discussions with @mariogrip about this code: It deserves to be split out as a separate "platform" in the same way that the "android" platform has been.
That's something I would again be happy to help out with, but I am currently finding the project a bit opaque in terms of actually getting engagement on tasks and priorities :-\