lalapps release request
@adam-mercer @duncanmmacleod The last lalapps release (6.26) was in late June. Since then, the one feature that would be really convenient for me to have in a release is the added feature (2nd commit) from !1373 (merged). Apart from that, the same MR also contains a feature removal (long deprecated before), and a few other changes have been done across the package, also including some more feature removals. However, since lalapps is the "last step" in the build chain and mostly includes stand-alone executables anyway, would it be ok to just do an "all commits since the last release of this subpackage...?
One issue though may be that some of those might require lalpulsar or lalburst updates, at which point we'd have a rebuild avalanche. If you don't have an automated way to check that, I can go at least through the lalpulsar-related changes and check.
If you prefer a release with just individual commits, @karl-wette and I can check if any of the other CW changes have priority (and whether they require lalpulsar updates), and @kipp.cannon please speak up if you'd like the burst changes included.
I couldn't get the gitlab "compare" interface to play along providing either a tag name or its corresponding commit against current master, so for convenience here's a local screenshot of commits that touched the lalapps
directory since 6.26:
Release details
Subpackage releases requested:
-
lal
-
lalframe
-
lalmetaio
-
lalsimulation
-
lalburst
-
lalpulsar
-
lalinspiral
-
lalinference
-
lalapps
Commit information
The following commits should be included in the release: (subject to further discussion)