Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2023.7.0 #173

Merged
merged 1 commit into from
Jul 7, 2023
Merged

Release 2023.7.0 #173

merged 1 commit into from
Jul 7, 2023

Conversation

jrbourbeau
Copy link
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@charlesbluca
Copy link
Member

@conda-forge-admin, please rerender

@jakirkham
Copy link
Member

jakirkham commented Jul 7, 2023

What are your thoughts on incorporating PR ( #171 ) as part of this release? Also related is PR ( conda-forge/dask-feedstock#226 )

Some background in this comment ( conda-forge/dask-feedstock#225 (comment) )

@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2023

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/dask-core-feedstock/actions/runs/5489100784.

@jrbourbeau
Copy link
Member Author

Thanks @charlesbluca @jakirkham

What are your thoughts on incorporating PR ( #171 ) as part of this release?

I'd prefer to release things as is and then we can always follow up with a build increment.

FWIW I don't feel very strongly about where these version pins are specified. That said, I don't think there are many people who need to rely on dask-core, so I wouldn't want to see us spend a bunch of time accommodating that situation (unless I'm wrong and there are lots of people who care about it).

If we were going to mix things up, having a conda versions of the various pip extras (e.g. conda install dask-array == pip install dask[array]) would probably be more valuable than making dask-core more usable. I know this has caused some confusion in the past and come up a few times. Again, not necessarily pushing strongly for this either. I just think that might be more valuable, if we were to do something in this space at all

@jrbourbeau jrbourbeau merged commit efea463 into conda-forge:main Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants