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

v0.9.2 release plan #1506

Closed
9 tasks done
cwhanse opened this issue Jul 26, 2022 · 10 comments · Fixed by #1534
Closed
9 tasks done

v0.9.2 release plan #1506

cwhanse opened this issue Jul 26, 2022 · 10 comments · Fixed by #1534
Labels
Milestone

Comments

@cwhanse
Copy link
Member

cwhanse commented Jul 26, 2022

@kandersolar kandersolar added this to the 0.9.2 milestone Jul 26, 2022
@kandersolar
Copy link
Member

Can we drop python 3.6 support in this release? GitHub Actions is dropping it in MacOS pretty soon, it's way past the NEP29 and Python end-of-life windows, and pvanalytics and rdtools have already moved to >=3.7.

@mikofski
Copy link
Member

I’m ok to drop 3.6 ✅

@adriesse
Copy link
Member

I guess I can't edit this myself, but I would like the spectral mismatch PR to go into this release because I would like to use the new functions in an example notebook to accompany a new open data set.

@wholmgren
Copy link
Member

Releasing on pypi and conda-forge is a couple minutes of work. We should just do it this week whatever we have. It would be really nice to speed up the release cadence and make it less of a big deal.

@kandersolar
Copy link
Member

Unless someone already has a branch started, I will submit a PR shortly for final 0.9.2 cleanup. Doesn't mean we can't do some last minute feature merges if the reviewing capacity is available (unfortunately I myself am unlikely to review anything else before the release); I'm just getting antsy about getting this out the door before PVPMC.

@wholmgren
Copy link
Member

@kanderso-nrel go for it. I'm +1 on #1478 if you think it's ready.

@cwhanse
Copy link
Member Author

cwhanse commented Aug 19, 2022

I edited the checklist to defer PRs that aren't quite ready (either need reviews or author responses). The only one to decide is #1478

@kandersolar kandersolar mentioned this issue Aug 19, 2022
5 tasks
@adriesse
Copy link
Member

As I explained above, it would be nice to have the mismatch feature released fairly soon. If it is not in this release, how much time do we think might elapse before the next release?

@wholmgren
Copy link
Member

@adriesse if a pre-release is acceptable then we can make that within minutes of merging the PR. git fetch upstream; git rebase upstream/master; git tag v0.9.3-alpha.1; git push upstream v0.9.3-alpha.1; wait a few minutes and then pip install pvlib --pre. In principle we can make that a full release - the only complication is the build for the pvlib channel is manual and can be tedious (see the release notes wiki). Finishing the what's new is tedious when the release grows to the current size, but easy if there's only a couple of items. If you want to take on the what's new prep then it would help get the release out the door faster. So, somewhere between minutes, days, and 1-3 months depending on needs/desires/contributions.

@adriesse
Copy link
Member

I don't think it's so critical that it warrants exceptional actions, but perhaps we could consider 9.3 in 2-3 weeks? My temperature PR should be done then too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants