You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is composed of a few different parts:
C++ library for streaming 3D Tiles into a USD stage
Python library that wraps the C++ streaming library
Omniverse Kit extension - front-end UI that can be added to Omniverse Code, Omniverse Create
... future libraries
... future kit extensions
Are these versioned separately or together? The kit extension version is here and the change log is here. This is what's shown when loading the extension in Omniverse Code/Create. Meanwhile the C++ library version is here. If we want to version everything together we need to be careful that these don't get out of sync.
I think it makes more sense if the C++/Python library are versioned separately from the Kit extensions since the C++ library may have users outside of the Omniverse ecosystem.
The text was updated successfully, but these errors were encountered:
For each new release increment extension version (in extension.toml) and update the changelog (in docs/CHANGELOG.md). Semantic versionning must be used to express severity of API changes.
This project is composed of a few different parts:
Are these versioned separately or together? The kit extension version is here and the change log is here. This is what's shown when loading the extension in Omniverse Code/Create. Meanwhile the C++ library version is here. If we want to version everything together we need to be careful that these don't get out of sync.
I think it makes more sense if the C++/Python library are versioned separately from the Kit extensions since the C++ library may have users outside of the Omniverse ecosystem.
The text was updated successfully, but these errors were encountered: