-
Notifications
You must be signed in to change notification settings - Fork 1.1k
v0.9.4 release plan #1608
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
Comments
List looks OK to me. |
I'd like to get this release wrapped up in the next day or two before reviewers drift away for the holidays (assuming they haven't already). #1602 needs a green checkmark from @cwhanse. #1598 is a conflict-creating pest that I want to merge last so that the burden of making sure nothing gets lost is on myself. Should we add #1617 and #1618 to the list? They are small and easy to review but are not currently tagged with a milestone. |
I'm -1 on last minute API changes to well-loved functions. Seems to me that deprecation of |
@wholmgren I don't mind revisiting any decisions here. To clarify, are you suggesting (1) reverting #1558 and (2) adding the new functionality in #1602 to |
@wholmgren could you be more specific about what you do and don't like? Top two scenarios for moving forward? |
My recommendations are:
|
I'm okay with keeping |
Sounds like a plan! |
Open candidates for inclusion:
pvwatts
topvwattsv5
everywhere #1558 and Revert "Renamepvwatts
topvwattsv5
everywhere (#1558)" #1619Things to defer:
iotools.get_psm3
may need some updates for the new 2021 data #1591@pvlib/pvlib-maintainer please edit as you see fit. Any objection to choosing the
15th19th20th as target release date?The text was updated successfully, but these errors were encountered: