-
Notifications
You must be signed in to change notification settings - Fork 28
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
Release v2.2.0 #231
Comments
@lrapetti I agree with it. I hoped to had test/devel-rebase tested before making a new release, as this would have enabled to pull in the changes from #181 to upstream. NOTE: PR link above update from original posting However, at this point it is cleaner have a release from merging devel to master.
Good call. This will make things aligned with how wearable is maintained too. |
Before the release, may be checking the config yarp manager files for iCub visualization through #230 can be useful to have tested and committed to upstream for the next iteration of tests for retargeting. |
The main problem there is that it depends on a branch of |
Windows CI failed on push flow after merge at https://github.com/robotology/human-dynamics-estimation/runs/1790878536#step:9:10886, looking for |
The failure has now been fixed (#232), @Yeshasvitvs we can create the new release, what do you think? |
No, I am not planning any change, for me we can proceed with the release. |
@lrapetti and I did the new release https://github.com/robotology/human-dynamics-estimation/releases/tag/v2.2.0 |
Expecting an automatic update of robotology-superbuild, similar to robotology/robotology-superbuild#607 |
@lrapetti We can open a separate issue for this task, and also align https://github.com/robotology/wearables with release tag branches |
Just to clarify, not using devel is a strategy that make sense and I think it make sense to use for you, but it is not used by all robotology projects. At the moment is used by YARP and YCM, but not (for example) by icub-main . At the moment the |
Cross linking the comment from @traversaro #233 (comment). In brief this release is currently not aligned with the stable branch of iDynTree if |
FYI that scripts runs every sunday night (see https://github.com/robotology/robotology-superbuild/blob/8f415ed824730de37d886806e1db58d88117a6be/.github/workflows/update-latest-releases.yml#L9), so if you want to bump the release before manually feel free to do so. |
The last release was done almost one year ago with the
v2.1.0
tag, and since then new features have been released. I think it's time to release it.Indeed we should proceed:
devel
intomaster
I think also we might align with the rest of
robotology
removing thedevel
branch, keeping the released tags as stable code pointers, and usingmaster
as development branch.cc @Yeshasvitvs @traversaro @diegoferigo
The text was updated successfully, but these errors were encountered: