I agree for proceeding with the release process. We are admittedly a little
light on new developments, but we have at least one major improvement that
has been critical in at least 2 projects utilizing SDAP.

I do have one PR outstanding in the ingestor repo with an attempted fix for
a small but nasty bug.

-Riley

On Wed, Jan 21, 2026, 7:46 PM Nga Chung <[email protected]> wrote:

> Hi all,
>
> A new release for SDAP is long overdue as version 1.4.0 was released over a
> year ago, so I'd like to use this thread to assess how the SDAP community
> feels about going ahead and cutting a 1.5.0 release with all the changes
> since 1.4.0.
>
> From the CHANGELOG.md, unreleased changes include:
>
> For SDAP Ingester
>
> https://github.com/apache/sdap-ingester/blob/develop/CHANGELOG.md#unreleased---unreleased
>
> ### Added
> - SDAP-534: Added proper support for data variables in NetCDF groups. Can
> handle multiple data variables across different groups. Coordinates are
> still required to be in root.
> ### Fixed
> - Fixed issue with Collection Manager Docker build failing due to
> setuptools issue
>
> For SDAP Nexus
>
> https://github.com/apache/sdap-nexus/blob/develop/CHANGELOG.md#unreleased---unreleased
> ### Added
> - Helm chart option to associate AWS IAM role to the SDAP Spark
> ServiceAccount (EKS only).
> - SDAP-517: Added new options for AWS credential management for dataset
> backends relying on data in S3.
>   - Profile `config.aws.profile` takes creds from named AWS profile
>   - Can omit credentials entirely to source from environment
>   - Dynamic DAAC credentials: Gets dynamic credentials from NASA EOSIDS
> DAACs (requires Earthdata Login; only works in `us-west-2` AWS region)
> ### Changed
> - SDAP-533: Updated Helm chart
>   - Updated ingress dependency chart
>   - Fixed values.yaml for Solr
> ### Fixed
> - SDAP-531: Tomogram/Tomogram3D: Fix bug for min/max elevation == 0
> - SDAP-540: Add mutex around Solr operations for dataset add/update/delete
> to fix possible concurrency issue
>
> I think we should go ahead and ready the release for a vote. This will at
> least help us get a refresher on our release process and give us the
> momentum to have more frequent releases.
>
> Best,
> Nga
>

Reply via email to