conda-package-handling
conda-package-handling copied to clipboard
Release 2.3.0?
There are a couple nice changes in the news/
folder. What about merging https://github.com/conda/conda-package-handling/pull/231 and cutting a new release?
Summary
Placeholder for conda-package-handling YY.M.x
release.
Pilot | dholth |
---|---|
Co-pilot | jezdez |
Tasks
The week before release week
- [x] Create release branch (named
release-2.3.0
) - [x] Ensure release candidates are being successfully built (see
conda-canary/label/rc-conda-package-handling-YY.M.x
) - [x] Complete outstanding PRs
- [x] Test release candidates
Release week
- [x] Create release PR (see release process)
- [x] Publish release
- [x] Merge
YY.M.x
back intomain
- [x] Activate the
YY.M.x
branch on ReadTheDocs - [ ] Feedstocks
- [ ] Bump version & update dependencies/tests in Anaconda, Inc.'s feedstock
- [ ] https://github.com/AnacondaRecipes/conda-package-handling-feedstock/pull/13
- [x] Bump version & update dependencies/tests in conda-forge feedstock
- [ ] https://github.com/conda-forge/conda-package-handling-feedstock/pull/76
- [ ] Bump version & update dependencies/tests in Anaconda, Inc.'s feedstock
- [x] Hand off to the Anaconda packaging team
- [ ] Announce release
- Blog Post (optional)
- [ ] conda.org (link to pull request)
- Long form
- [ ] Create release announcement draft
- [ ] Discourse
- [ ] Matrix (conda/conda) (this auto posts from Discourse)
- Summary
- Blog Post (optional)
@conda/conda-core thoughts?
I'd be happy to help with this.
Thanks @travishathaway. Looks like @dholth has a PR at #243 which is simple enough to make it to the merge queue. I guess we can start the release process after that. I'm not sure which process that is though. Rever?
#243 also includes code coverage improvements for cph list
Ping @dholth, are we ready now? It looks like the merge queue is clear :D
Yes, we should do a release.
Closing since 2.3.0 was released.