-
Notifications
You must be signed in to change notification settings - Fork 48
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
Set default of ROBOTOLOGY_PROJECT_TAGS to Custom and fix release problems #352
Conversation
Actually running this in CI is more complicated then expected. The problem is that in the current GitHub Actions scripts, the
releases/2020.02 branch, and then think for 2020.05 a more permanent solution.
|
Great, the CI is finally failing so it means that is actually running. : ) |
Otherwise ROBOTOLOGY_PROJECT_TAGS_CUSTOM_FILE is ignored
d347a84
to
2606722
Compare
There was a problem in the icub-gazebo URL, fixed by 2b958f9 . |
Ok, finally some real problems that we did not have on
This is due to robotology/human-dynamics-estimation#174 and robotology/human-dynamics-estimation#171 (comment) , and the fix is apparently not provided in
This is robotology/unicycle-footstep-planner#33 . It has been fixed in iDynTree in robotology/idyntree#642, but the fix is not part of iDynTree v1.0.1 . @traversaro can you please tag a v1.0.2 with this fix? |
Done in robotology/idyntree#650 . |
@traversaro we updated the master branch with the latest changes in devel following the PR robotology/human-dynamics-estimation#164. After the CI checks are done, we will tag the master with |
The CI checks seems to have a failure, but related to the deployment of the documentation, not of the library itself, so if you could tag v2.1.0 it would be great. |
fyi @lrapetti @Yeshasvitvs |
Thanks! Just to understand, at the CMake level the version is still 2.0.0 (See https://github.com/robotology/human-dynamics-estimation/blob/269a08c2a282f87da3dad788e31b502ccc542409/CMakeLists.txt#L8) , this is not a big problem, but it may be confusing for downstream projects if they actually want to enforce the dependencny on 2.1.0 and its new features. |
@traversaro The version of |
The compatibility rule is defined in OsqpEigen, and in the update from 0.4 to 0.5.2 the compatibility rules has changed to |
Otherwise
ROBOTOLOGY_PROJECT_TAGS_CUSTOM_FILE
is ignored, for future reference this is necessary for all thereleases/*
branches, i.e. #350 is incomplete.