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.10.0 release plan #1735

Closed
kandersolar opened this issue May 16, 2023 · 9 comments · Fixed by #1793
Closed

v0.10.0 release plan #1735

kandersolar opened this issue May 16, 2023 · 9 comments · Fixed by #1793
Labels
Milestone

Comments

@kandersolar
Copy link
Member

Our next release is scheduled for mid June. We currently have a v0.9.6 milestone, but I suggest we merge it into the v0.10.0 milestone and release v0.10.0 next so that we can deal with this accumulation of breaking changes:

Any objections to the next release being v0.10.0?

@mikofski
Copy link
Member

good idea

@cwhanse
Copy link
Member

cwhanse commented May 16, 2023

No objections for me, but let's make a complete list of open issues/PRs to include.

@kandersolar kandersolar added this to the 0.10.0 milestone May 16, 2023
@kandersolar
Copy link
Member Author

kandersolar commented May 16, 2023

I've relabeled all the v0.9.6 items to v0.10.0, and then took the liberty of moving old items that aren't making progress into the someday milestone. Here is a complete accounting of what remains:

PRs with breaking changes in need of review:

Other PRs that are in need of review but don't need to go in a *.*.0 release:

Deferred to the future:

Let's wait to migrate the existing 0.9.6 "what's new" content over to the 0.10.0 file until the finalization PR so that we don't create a bunch of unnecessary merge conflicts in the open PRs.

@kandersolar
Copy link
Member Author

Should we remove forecast.py in v0.10.0? It was deprecated in v0.9.1 (released March 29, 2022).

@adriesse
Copy link
Member

adriesse commented Jun 7, 2023

I notice that we're a week from the mid-June target and about half of the proposed PR's are still open. And mid June coincides with PVSC as well as InterSolar in Europe. Do we need to adjust 'what' or 'when'?

@kandersolar kandersolar mentioned this issue Jun 8, 2023
9 tasks
@kandersolar
Copy link
Member Author

Do we need to adjust 'what' or 'when'?

Probably both. Seems like reviewer capacity is pretty limited at the moment. I guess it might be slightly nicer to not make a new version with breaking changes right after Mark and Silvana's tutorial at PVSC, but overall I don't mind doing the release in "mid-late June".

@kandersolar
Copy link
Member Author

@pvlib/pvlib-maintainer Time to get back to reviewing now that people are back from conferences! I'd like to finalize v0.10.0 next week.

This PR that should not be deferred to 0.10.1 is still in need of review:

The following PRs have at least one approving review and I plan to merge them on Friday June 23. If you think you might object, please review them before then, or at least indicate the desire to review.

If you want any additional PRs to be included in 0.10.0, please list them below. Otherwise, I'll plan to push the remaining items (all additive) in the v0.10.0 milestone to v0.10.1.

@mikofski
Copy link
Member

Ready for takeoff

@cwhanse
Copy link
Member

cwhanse commented Jun 27, 2023

Include fixing #1731

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.

4 participants