develop branches point to NDSL tagged releases instead of NDSL/develop

[oelbert]

in setup.py we list ndsl as a dependency, but only the latest release. This slows development because any features or updates to NDSL have to be released before we can then get relevant tests to pass in PyfFV and PySHiELD:

PyFV3/setup.py

Line 23 in 1b2057f

ndsl_requirements = ["ndsl @ git+https://github.com/NOAA-GFDL/NDSL.git@2025.03.00"]

Since we're using the develop branches of all 3 repos for development should we have the setup.py in the develop branches of PyFV3 and PySHiELD point to the develop branch of NDSL in order to fix this?

[fmalatino]

This makes sense to me, but then would we require a custom installation method for which version of NDSL that we would like installed? Or should we institute release branches for pyFV3 and pySHiELD that point to the current release of NDSL?

[jjuyeonkim]

A related PR is: #50
This PR has a TODO to fix the sw_dynamics flag.

[oelbert]

This makes sense to me, but then would we require a custom installation method for which version of NDSL that we would like installed? Or should we institute release branches for pyFV3 and pySHiELD that point to the current release of NDSL?

I think this is where the difference between the main and develop branches can be helpful for us. develop can point to ndsl/develop and main can point to a tagged release

[romanc]

This was done with PR #59. Can we close this issue?

[fmalatino]

My vote is yes, but will let @oelbert make the final decision.

[oelbert]

👍 👍 👍