search

libLAS / libLAS

C++ library and programs for reading and writing ASPRS LAS format with LiDAR data
http://liblas.org
Other
309 stars 158 forks source link

New release? 1.8.2 first, then 1.9.0 or 2.0.0? #146

Open fxcoudert opened 6 years ago

fxcoudert commented 6 years ago

There are a number of patches that need to be used to compile with recent GDAL and clang (Xcode >= 9). Could you please release a version of gdal, so that we can ship it to users of Homebrew? (and I am sure other distros will like it a lot as well!) Thanks

hobu commented 6 years ago

I think the biggest holdup for a release has been catching libLAS up to LASzip 3.x. That's a big chunk of work that hasn't been done, but I'll see about rolling out a release for the current state of the software.

mloskot commented 6 years ago

Perhaps there could be libLAS 1.9 based on the current master and wait with libLAS 2.0 for LASzip 3.x.

mloskot commented 4 years ago

FYI, there has been a small but critical bug fix applied, see https://github.com/libLAS/libLAS/pull/168#issuecomment-547420372

mloskot commented 4 years ago

FYI, over the weekend, as prep for 1.8.2 which likely is going to be issued first as bug fix release, I started collecting the release notes:

https://github.com/libLAS/libLAS/blob/096bb67d3cc7dcda4b44af9769e2b33d89587e56/RELEASE_NOTES.md

This is in Markdown, but I aim to convert it to reStructuredText for integration with the docs.

SunBlack commented 1 year ago

@mloskot Could you make a point release? In most cases, you tell others a specific tag to build because you don't want the latest changes in it until they are stable. However, the last release here was ages ago and there are a few CVEs that have been fixed, so a new version number would be nice.

mloskot commented 1 year ago

@SunBlack I'm being a bit swamped and I doubt I'll have time sooner than next week. Would you be willing to help us with the release? I'm fairly sure we can arrange commit access for you, any objections @hobu ?

SunBlack commented 1 year ago

That has time, just wanted to note that a new tag would already be handy. I actually only came back to this library here, because it was installed with vcpkg once as a dependency, even if I still do not know why. We use another library for LAS files, because this one doesn't support LAS 1.4. Since this library was even removed from the Debian sources, the question would be whether it is worthwhile to continue the library (there are also LASTools and PDAL, which also have disadvantages here, but are more strongly promoted), or you set a final tag, so that all who still use it get a version with the latest patches and you archive the project afterwards.

mloskot commented 1 year ago

We use another library for LAS files, because this one doesn't support LAS 1.4. Since this library was even removed from the Debian sources, the question would be whether it is worthwhile to continue the library

Well, libLAS status has been explained in the docs, but it looks like it's worth displaying it in the repo landing page https://github.com/libLAS/libLAS/commit/6503043f3636ecf9588086c007ef61d9acb48fff