Skip to content

Release 2.3.2? #433

Closed
Closed

Description

@jakirkham

Would it be alright to cut a patch release? Thoughts @zarr-developers/core-devs?

Activity

  1. alimanfoo commented on May 1, 2019

    @alimanfoo
    Member

    No objections here. Looks like there isn't an entry in release notes for the changes in #427.

  2. jakirkham commented on May 1, 2019

    @jakirkham
    MemberAuthor

    @QuLogic, would you have time to submit a PR for the changelog entry? If not, I can give it a look later.

  3. jakirkham commented on May 6, 2019

    @jakirkham
    MemberAuthor

    Given this is just a minor test change, I'd rather not hold up the release.

  4. shikharsg commented on May 6, 2019

    @shikharsg
    Contributor

    Any chance of getting #306 into the 2.3.2 release? In which case I will document it in docs/release.rst.
    Or is this something that is more appropriate when we do a 2.4 release?

  5. jakirkham commented on May 6, 2019

    @jakirkham
    MemberAuthor

    As it is adding new functionality, it should be targeting 2.4. Though I agree it would be exciting to get that integrated. 🙂

  6. jakirkham commented on May 22, 2019

    @jakirkham
    MemberAuthor

    Looks like there isn't an entry in release notes for the changes in #427.

    Doing this in PR ( #441 ).

  7. jakirkham commented on May 30, 2019

    @jakirkham
    MemberAuthor

    Have completed the release. Packages on PyPI and conda-forge. Sorry for the delays.

  8. alimanfoo commented on May 30, 2019

    @alimanfoo
    Member

    Thanks a lot John 👍

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