-
Notifications
You must be signed in to change notification settings - Fork 417
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
Tag for 0.6.0 and Updated readme #343
Comments
A very popular topic the last month or so: #329 (and then it links to others). I think it's largely a case of figuring out if there are any stray threads that are in flight that we want in 0.6.0 and then pulling the trigger. |
Yes, agreed. But until then, atleast the readme and the documentation should be updated to reflect the changes or it kills the purpose of using the master branch. I should be hopeful of a tagged 0.6.0 soon. Thanks. |
At least recently, PRs have been pushed toward updating the change log. I don't know how far back that goes and it might require some exploration to make it more comprehensive prior to 0.6.0. But there's some progress in that regard. |
Though the documentation available here is for FCL version 0.6.0, I don't see a tagged version in the source. I believe it the master branch touted as 0.6.0, isn't it?
For someone who is using standardized versions and creating dependencies out of that, it would be very helpful to create a new ASAP because the file structure and import headers have all been changed from 0.5.0 to 0.6.0 (the master branch!).
Recent commits on the master like Eigen transform mode change from AffineCompant to Isometry changes a lot fo things and the readme does not reflect it.
Do these suggestions sound reasonable?
The text was updated successfully, but these errors were encountered: