About closed tickets and new version

Nobody has claimed this yet.

Hey everyone,

I’ve gone ahead and marked the old v2.1.1 tickets as “completed” so we can start v3 with a clean slate. This should make it much easier to track new issues going forward. And in many ways, v3 is effectively the “fix” for v2.1.1 anyway.

The sdk3 branch will become the main branch soon.

For those who haven’t heard this before: the sdk3 branch represents the new Mapbox Unity SDK. It’s not really a traditional version update, it’s more of a ground-up rework. That comes with both pros and cons. One important thing to note is that migration from v2.1.1 to v3 isn’t straightforward and will require some development effort and care. Also I guess it can be said v3 has fewer features (for example, no AR support yet).

Documentation is still limited and there’s no official migration guide at the moment, but we expect this to improve over time. For now, we decided there’s no reason not to share this openly.

- v3 supports unity editor 2020.3 for now but some future features will require 2022.3+
- It only supports iOS and Android builds at the moment. Windows desktop support will be explored soon.
- No augmented reality or virtual reality helpers/support in the package.

Read the sdk3 branch and the release information in this issue first; no files, tests, or implementation entry points are named. The issue mentions limited documentation and a missing migration guide, but it does not define the guide's scope or completion criteria.

Written by the indexing model from the issue text.