-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T256 and development branch #11612
Comments
Hi @yosoufe master - this branch contains production code. All development code is merged into master in sometime, usually before releasing a formal release of librealsense. I think it's better to use always the master branch, since all releases are tagged from this branch. Regarding your question about T265, I think you can always use the code prior to these PRs changes, and continue using librealsense and ROS2 wrapper with your T265. @MartyG-RealSense, any other advices here? |
Does this mean that the code will not be maintained anymore neither by intel nor by the community? |
Unfortunately, It seems so |
Hi @yosoufe |
Hello, I have a question regarding the
development
branch and T265 support.development
branch? Should we use themaster
ordevelopment
branch?development
branch in Remove TM2 (T265) from LibRS #11287. and also it is removed from the ROS 2 wrapper onros2-development
branch in T265 clean up realsense-ros#2611.What should I do if I want to get the T265 working with ROS 2 now?
The text was updated successfully, but these errors were encountered: