Skip to content

Release v2.10 #5124

Closed
Closed

Description

@IAlibay

We want a new release of v2.10 ahead of the 2025 UGM.

Target release start date: ASAP (latest 15th October)

Blocking PRs:

@MDAnalysis/coredevs is there anything else you want to do include in this release?

Activity

  1. self-assigned this
    on Oct 12, 2025
  2. orbeckst commented on Oct 13, 2025

    @orbeckst
    Member

    (I merged PR #5113 , which wasn't on the original list, an hour ago as it was complete.)

  3. orbeckst commented on Oct 14, 2025

    @orbeckst
    Member

    No more PRs from my side to include urgently.

  4. IAlibay commented on Oct 15, 2025

    @IAlibay
    MemberAuthor

    Ok since no one else raised anything else, we will go ahead with the release.

  5. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    Are we making the conda-forge imdclient package a full dependency of the MDAnalysis cf package? I thought so but that shapes a bit how to write PR MDAnalysis/UserGuide#430

    (For the pip package it's optional in extras.)

  6. IAlibay commented on Oct 15, 2025

    @IAlibay
    MemberAuthor

    @orbeckst - I'm strongly voting no here. I'm not sure there's much room for discussion. As far as I can tell imdclient imports MDAnalysis. We can't have a package that depends on MDAnalysis also be a dependency of MDAnalysis, that's how we ended up breaking the MDA package and causing a ton of headaches with circular imports.

  7. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    imdclient does not have MDAnalysis as a dependency (only for tests). It only depends on numpy.

  8. IAlibay commented on Oct 15, 2025

    @IAlibay
    MemberAuthor

    I see, thanks for the clarification. I still vote no - I don't want to add more work to this release.

  9. IAlibay commented on Oct 15, 2025

    @IAlibay
    MemberAuthor

    (I note, given it's not a hard dependency block - this is a coredev vote [unless it becomes a headache / too much work])

  10. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    Ok, I defer to you here.

    We can revisit in the future (given that other file format packages such as gsd, h5py, pytng are bundled – https://github.com/conda-forge/mdanalysis-feedstock/blob/9f699f3281a3ab29b7594404e3c6c457b197d6df/recipe/meta.yaml#L36 ).

  11. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    Future discussion:

    • I don't see chemfiles in the run deps of the cf package. When did we drop that one? (It provides additional flexibility and formats.)
    • We also don't have RDKit installed automatically. (Important for "chemistry aware MDAnalysis")
    • We could probably just add duecredit. (Encourage citation best practices.)
  12. IAlibay commented on Oct 15, 2025

    @IAlibay
    MemberAuthor

    @orbeckst my suggestion is that we do a release with the cf package deps "as-is". In the meantime, if you (or another coredev) can start the discussion on voting for "what deps should we ship with", we can do another build release with more deps.

    Edit: when I say "build release", I mean we just increment the 2.10 build on conda-forge, with more/less deps.

  13. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    Totally agree!

  14. orbeckst commented on Oct 15, 2025

    @orbeckst
    Member

    (sorry, wrong button, didn't mean to close)

  15. IAlibay commented on Oct 18, 2025

    @IAlibay
    MemberAuthor

    The base library package is up on conda-forge, but we hit some issues with the py3.14 migration. This means that a) we don't have py3.14 out yet, b) MDAnalysisTests hasn't been released yet, c) if you own a package downstream of MDAnalysis, you might get a py3.14 migrator bot from conda-forge that doesn't actually work (because MDAnalysis didn't finish its migration).

    Working on a solution this evening.

  16. IAlibay commented on Oct 18, 2025

    @IAlibay
    MemberAuthor

    Ok, manual migration went through, both MDAnalysis and MDAnalysisTests packages are up on conda-forge. Release is done.

  17. orbeckst commented on Oct 19, 2025

    @orbeckst
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions