search

flexible-collision-library / fcl

Flexible Collision Library
https://flexible-collision-library.github.io/
Other
1.35k stars 414 forks source link

Update changelog and package.xml to 0.7.0 #547

Closed j-rivero closed 2 years ago

j-rivero commented 2 years ago

Following https://github.com/flexible-collision-library/fcl/issues/532 and after checking with @scpeters and @SeanCurtis-TRI I think we are ready to run a new fcl version, 0.7.0.

I've included everything I found in https://github.com/flexible-collision-library/fcl/compare/v0.6.1...master in the Changelog. Fixes https://github.com/flexible-collision-library/fcl/issues/532

This change is Reviewable

j-rivero commented 2 years ago

nit: 2021-09-xx now

Thanks @sherm1 ! I've set the release date to today.

j-rivero commented 2 years ago

OK, I'll merge this now. What else do we need to do to complete the 0.7.0 release?

Thanks Michael. We need to run a new release in github. Going probably to https://github.com/flexible-collision-library/fcl/releases/new , Following previous release, we can use v0.7.0 as the tag, FCL 0.7.0 as tittle, and in the summary maybe just copy paste the Changelog.

sherm1 commented 2 years ago

@scpeters is working on that. Current question is whether the version tag should be 0.7.0 or v0.7.0. Any opinion @j-rivero?

j-rivero commented 2 years ago

@scpeters is working on that. Current question is whether the version tag should be 0.7.0 or v0.7.0. Any opinion @j-rivero?

I think that it would be good to follow the previous schema. Said that, I looked into the releases and tags again and seems like only the 0.6.1 was done using the prefix v but there is also a 0.6.1 tag without prefix. With this, probably the best option is back to use 0.7.0 without v. Thanks @sherm1 , @scpeters

sherm1 commented 2 years ago

OK, thanks @j-rivero -- I'll publish the release with tag 0.7.0 tomorrow unless anyone objects. We can always add a v0.7.0 tag to the same commit later if anyone cares.