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
I was wondering if you plan to eventually either tag or release the software in this repo? While it is already possible to install in a reproducible way a specific version of lerobot via:
having releases would be convenient for the following reasons:
It is easier to express compatibility bounds (i.e. I know that my software is compatuble with lerobot >= 0.1.2 and lerobot < 0.2.5, while expressing this with raw commits is tricky)
It can be used to upload versions to pip (for example, as of May 2025 pip install lerobot works fine, but it install a really old versions of lerobot). This may permit for example to upload to PyPI software that depends on recent features of lerobot.
I briefly searched if there were already discussion on this but I could not find any issue or discussion related to that, if there is something that I overlooked, feel free to let me know, thanks.
The text was updated successfully, but these errors were encountered:
Just to clarify, note that even if there is no strict back-compatibility policy, the aforementioned advantages of tags and release still hold. I just wanted to point this out, as it is common to conflate "doing tag/releases" with "doing a tag and doing long-term mantainance of that version", while this issue was only asking about doing tags, not about anything else.
Thanks a lot for all the great work on lerobot!
I was wondering if you plan to eventually either tag or release the software in this repo? While it is already possible to install in a reproducible way a specific version of lerobot via:
having releases would be convenient for the following reasons:
pip install lerobot
works fine, but it install a really old versions of lerobot). This may permit for example to upload to PyPI software that depends on recent features of lerobot.I briefly searched if there were already discussion on this but I could not find any issue or discussion related to that, if there is something that I overlooked, feel free to let me know, thanks.
The text was updated successfully, but these errors were encountered: