We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi everyone! For Gazebo 11 Windows packaging, it would be nice to make a release of the ign-fuel-tools4 branch, as it includes a critical bug fix for Windows: #178 . The required changes in ignition-common3 (gazebosim/gz-common#197) were already release in 3.13 (see https://github.com/ignitionrobotics/ign-common/tags).
cc @Tobias-Fischer
An alternative we tried in conda-forge/libignition-fuel-tools-feedstock#32 (comment) was to backport the patch to an earlier release, but unfortunately it does not apply cleanly.
I guess following the standard release process will be ok.
This came out in conda-forge/libignition-fuel-tools-feedstock#32 (comment) .
The text was updated successfully, but these errors were encountered:
Seems like this can be closed - thanks @chapulina!
Sorry, something went wrong.
Thanks a lot!
No branches or pull requests
Desired behavior
Hi everyone! For Gazebo 11 Windows packaging, it would be nice to make a release of the ign-fuel-tools4 branch, as it includes a critical bug fix for Windows: #178 . The required changes in ignition-common3 (gazebosim/gz-common#197) were already release in 3.13 (see https://github.com/ignitionrobotics/ign-common/tags).
cc @Tobias-Fischer
Alternatives considered
An alternative we tried in conda-forge/libignition-fuel-tools-feedstock#32 (comment) was to backport the patch to an earlier release, but unfortunately it does not apply cleanly.
Implementation suggestion
I guess following the standard release process will be ok.
Additional context
This came out in conda-forge/libignition-fuel-tools-feedstock#32 (comment) .
The text was updated successfully, but these errors were encountered: