Skip to content

lalpulsar backwards-(in)compatible release request

@duncanmmacleod @adam-mercer we'd like another lalpulsar release already, but this time unfortunately due to !2024 (merged) it will be backwards-incompatible. Though in Karl's words:

With everything moved out of LALApps, it should hopefully be straightforward to build LALPulsar packages with ABI-breaking changes (when necessary) without triggering rebuilds of lots of downstream packages

As a heads-up, in a few weeks, we'd then need yet another, again backwards-incompatible, release containing at least !2027 (merged) and !2028 (merged). But we need to split this into two steps so that PyFstat (one of the few external packages depending on lalpulsar) can do an intermediate release pinning to this one, before the larger changes from those MRs.

@karl-wette can you confirm if the lalpulsar changes alone from !2024 (merged) work on their own and should resolve #604 (closed), or do we need a (backwards-compatible in this case) co-release of lal for the general SWIG fixes?

Release details

Subpackage releases requested:

  • lal
  • lalframe
  • lalmetaio
  • lalsimulation
  • lalburst
  • lalinspiral
  • lalinference
  • lalpulsar
  • lalapps

Commit information

The following commits should be included in the release:

Edited by Karl Wette