THE 2023 release #544
THE 2023 release #544
Conversation
Breaking changes: - Use the new yaml-cpp API, i.e. version 0.5+. - No longer provide sources in the contrib directory.
Update README.md
Update to doc, no need to wait for python binding test result
Disable static boost linkage by default
refactor: Drop support for yaml-cpp old API
Fix Transformations test build when using Eigen3.4
…s_in_debug Fix 2D transformation tests in debug
|
I've merged PR #546 in the release. Those are mainly fixes and stabilisation improvement related to the build-system and additions to the repository management: Build-system related
Repository management related
|
|
No stress @boxanm, I think you can take the time that you need. People have been waiting for a new release for a few years, they can wait for a few more days. I've notified those that were experiencing install/compiling issue to use the |
|
@pomerlef I've also added instruction and references to gently guide contributor toward adopting the Conventional Commit specification in their workflow so that we can later use semantic-versioning to automate release process. It's too soon to enforce its uses since libpointmatcher contributors already have an establish workflow and need some kinds of heads up. See |
… TeamCity badge; cleaned html formating
@boxanm I'm bypassing the branch protection rule since all test has passed and @simonpierredeschenes approved the the change as a code owner. The missing check was due to a miss-configuration in the `CODEOWNERS` file that required an approval by @pomerlef on all changes to the codebase. I'll push a fix so that he receive request for selected files that require admin oversight and keep the rest of the codebase under the responsibility of the maintainer group
…view request only for high-level file. Updated submodule to latest.
…ementation-and-refactor-out-to-NBS-generic-install-logic-NMO-436
…have cloned the repo [NMO-353] - feat: implemented a user side installer script for libpointmatcher dependencies and libpointmatcher (it call the build system version under the hood) - fix: solved the logic for passing CMAKE_INSTALL_PREFIX flag to the sourced installer sub-script - feat: added a `--test-run` flag plus dry-run logic to `lpm_install.*.bash` script for efficiently testing `lpm_install.*.bash` and `libpointmatcher_[dependencies_]installer.bash` scripts - fix: solved the build system installer git checkout tag landing out of the if clause on the parent level - test: added build system installer related bats test - test: added user installer related bats test - test: added `.env.libpointmatcher` bats test #### Others - ci(codeowner): update and clean entries - chore: added convenient run configuration for script help menu - update NBS and N2ST submodule to latest
…to stder on error [NMO-460]
…utput redirection to stder on error [NMO-457]
…tmatcher-turnkey-install-scripts-for-user-who-have-cloned-the-repo-NMO-353 feat: implement libpointmatcher turnkey install scripts for user who have cloned the repo
…sg ref, added convenient run config
|
|
@pomerlef I was wondering if we should put the new |
For approval by @pomerlef
Preparation for release version with commits spanning over close to 5 years.
Note: the code diff between the
releasebranch and themasterbranch wont reflect the breath of commit added to the proposed release version both in number and type.Even though there's no API breaking change, since there was a lot of major change and improvement, I propose that this release bump the repository version from to1.3.1→2.0.0.After discussion, will keep major no to 1 for the release
In this PR: