Skip to content

release v0.18.0 #5232

Closed
Closed

Description

@dcherian

As discussed in the meeting, we should issue a release soon with the new backend refactor and the new docs theme.

Here's a list of blockers:

Would be nice and look done:

Somewhat important, but no PR yet:

@TomNicholas and @alexamici volunteered to handle this. I can be online at release time to help with things if needed.

Release instructions are here: https://github.com/pydata/xarray/blob/master/HOW_TO_RELEASE.md

IIRC they'll need to be added to the PyPI list and RTD list.

Activity

  1. Illviljan commented on Apr 30, 2021

    @Illviljan
    Contributor

    May I suggest #4740, the only thing this needs I think is a rebase. I recently got a new computer and was reminded how slow the interpolation is without these changes.

  2. alexamici commented on Apr 30, 2021

    @alexamici
    Collaborator

    I propose the following timeline that is the fastest I can personally try:

    • Monday May the 3rd, feature freeze, please refrain from merging new features unless they are discussed here
    • during feature freeze everybody please help reviewing the PR in the list above
    • Thursday the 6th, target release day, the best would be to schedule a window for a couple of hours (?) for @TomAugspurger and me to going through the release steps together with @dcherian.

    @TomAugspurger and others does it work for you all?

  3. TomNicholas commented on Apr 30, 2021

    @TomNicholas
    Member

    @alexamici I think you tagged the wrong Tom, but yes that works for me.

  4. max-sixty commented on Apr 30, 2021

    @max-sixty
    Collaborator

    I think @alexamici 's plan is reasonable. I've had less of a process — no freeze etc — and that's worked fine — we do have a good test suite, and I've been really trying to make the release process a normal thing anyone can do in an hour.

    But it's your call (and there's not much practical difference).

    Thanks again!

  5. dcherian commented on Apr 30, 2021

    @dcherian
    ContributorAuthor

    IIRC they'll need to be added to the PyPI list

    We can avoid this by using the pypi github action thing to automatically build and upload when tagging a release on github. It uses a repo-level secret. Just a thought.

    and RTD list.

    I added @alexamici . @TomNicholas you need to sign up on RTD before I can add you there as a maintainer

  6. dopplershift commented on Apr 30, 2021

    @dopplershift
    Contributor

    We can avoid this by using the pypi github action thing to automatically build and upload when tagging a release on github. It uses a repo-level secret. Just a thought.

    $0.02 from an outsider is that this has served us exceedingly well on MetPy. Our release process has become:

    1. Close milestone
    2. Adjust the auto-generated draft GitHub release (summary notes)
    3. Click "publish release" -> packages uploaded to PyPI
    4. Merge conda-forge update from their bots

    It's almost more secure this way because the token from PyPI only has upload permissions--no need to store someone's password.

  7. TomNicholas commented on May 3, 2021

    @TomNicholas
    Member

    (@dcherian I've signed up on RTD now)

  8. keewis commented on May 3, 2021

    @keewis
    Collaborator

    great, you're a maintainer now (for pint-xarray, too, btw)

  9. dcherian commented on May 4, 2021

    @dcherian
    ContributorAuthor

    It'd be nice to bump our minimum dependency versions if someone has the time.

  10. alexamici commented on May 5, 2021

    @alexamici
    Collaborator

    Form what I can see the #5258 "bump versions" looks ready, someone with knowledge about minimum versions please merge it.

    After that is in, @dcherian you can probably uncomment the var._meta bit in #4740 "faster interp" and we can merge it as well. Again I'm not a user of that part of code, and I would feel more conformable if someone with more knowledge would click on the "merge" button.

    This leaves only #5235 as a blocker that has a failing test, a proposed fix by @keewis. but the OP hasn't responded yet. How should we handle it? This looks ready to merge now. Sorry @tomwhite I read the timestamps wrong. Great job!

  11. alexamici commented on May 5, 2021

    @alexamici
    Collaborator

    Any thoughts on merging #5244 and doing the v0.18.0 release via GitHub Actions?

    I'm using GA in a couple of repositories and I find them very handy, but I usually had to make a couple of releases before getting all the details right, which looks awkward to do with a high profile project like xarray.

    We could try release one or more release candidates and go for v0.18.0 only after we are sure the GA release procedure is working though.

  12. keewis commented on May 5, 2021

    @keewis
    Collaborator

    we could also temporarily switch the uploads to test.pypi.org to verify, create debug versions (rc candidates?) and switch back to pypi.org once we're confident

  13. kmuehlbauer commented on May 5, 2021

    @kmuehlbauer
    Contributor

    we could also temporarily switch the uploads to test.pypi.org

    Why not always upload pushes to master to test.pypi.org?

  14. keewis commented on May 5, 2021

    @keewis
    Collaborator

    I think that's because nobody had that idea, yet.

    Edit: that would also help with the idea in #5244 (comment). Let's continue that discussion in #5244

  15. alexamici commented on May 6, 2021

    @alexamici
    Collaborator

    @TomNicholas & @dcherian I'm having a look at the what's new, shall we set a time for going through the release process? do we want do the steps while in a call?

  16. 33 remaining items

  17. dcherian commented on May 6, 2021

    @dcherian
    ContributorAuthor

    Yup, nice work everyone!

    https://pypi.org/project/xarray/

  18. keewis commented on May 6, 2021

    @keewis
    Collaborator

    ah, right, only the "push tag" workflow run failed

  19. alexamici commented on May 6, 2021

    @alexamici
    Collaborator

    I'm testing after pip install -U xarray just to be on the safe side 😄

  20. TomNicholas commented on May 6, 2021

    @TomNicholas
    Member

    Alright I'll carry on with the other steps then I guess? 😅

  21. TomNicholas commented on May 6, 2021

    @TomNicholas
    Member

    How many xarray devs does it take to do a release? Answer: at least 5 apparently

  22. alexamici commented on May 6, 2021

    @alexamici
    Collaborator

    How many xarray devs does it take to do a release? Answer: at least 5 apparently

    🤦

    But next time it will be sooooooo smooth!

  23. andersy005 commented on May 6, 2021

    @andersy005
    Member

    maybe we should make the "upload to TestPyPI" a separate step?

    Or we could just set

    skip_existing: true

    on the upload to TestPyPI step.

  24. TomNicholas commented on May 6, 2021

    @TomNicholas
    Member

    Okay that should be everything except emailing the mailing lists, which I will try now

  25. alexamici commented on May 6, 2021

    @alexamici
    Collaborator

    12899 passed, 1145 skipped, 211 xfailed, 63 xpassed, 321 warnings on my Mac.

  26. alexamici commented on May 6, 2021

    @alexamici
    Collaborator

    @TomNicholas feel free to close the issue once you are done.

  27. TomNicholas commented on May 6, 2021

    @TomNicholas
    Member

    My email got bounced from pyaos@lists.johnny-lin.com because I'm not a member, but otherwise I think this is done. (I'm also not subscribed to numpy-discussion@scipy.org or scipy-user@scipy.org so maybe it's about to get bounced from there too).

  28. TomNicholas commented on May 6, 2021

    @TomNicholas
    Member

    I updated the release guide in #5274 by the way.

  29. dcherian commented on May 6, 2021

    @dcherian
    ContributorAuthor

    Nice work, @TomNicholas

  30. shoyer commented on May 6, 2021

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

Metadata

Metadata

Assignees

No one assigned

    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