v0.7.2 release planning

[CameronTStark]

I'm opening this issue to centralize the discussion of what will be in the v0.7.2 release. Please try to centralize your thoughts and discussion about the next release here or by numerical reference from another issue/PR E.g. #XYZ.

This is a new strategy proposed by @wholmgren and @cwhanse for someone assigned this role as "release manager" to track how current issues, PRs and bugfixes will add up to a release and ultimately perform that release. They've nominated me for this role for an undetermined amount of time so I'll do my utmost to stake this path through a continued dialoge with the community.

I plan to continue to utilize the v0.7.2 milestone as a means of communicating what is planned to go into the next release. This issue will be a forum for the the community to voice support for certain enhancements to be prioritized for the release that will then inform the milestones. Of course this could be disrupted by important bug fixes that need a quick release like for v0.7.1 but bumping the milestone version to the next release shouldn't add to the disruption. Overall I'll be reviewing the status of current issues and PRs for how they fit into a future release.

To start the conversation, please let me know what you think about what's currently listed on the v0.7.2 milestone and let me know if there's a reason to add more or remove something. Also, please suggest methods for making this process easier, faster or clearer.

Thanks for your support!

[kandersolar]

#764 got a lot of attention and seemed like it got close to the finish line but has been stagnant for several months. It would be good to see it get cleaned up and finished. I'd be happy to lead that if needed.

An unrelated thought not specific to 0.7.2 but releases in general: creating the next whatsnew file in master whenever a release is finalized would avoid some awkwardness in the first couple PRs afterwards. Maybe even create several whatsnew files ahead of time in preparation and just omit them from the main file until the time comes?

[cwhanse]

I've been working on this, I'll finish this week. I tried to contact @JPalakapillyKWH but got no response.

[CameronTStark]

I just added #764 to the 0.7.2 milestone based on your statement @cwhanse.

I am making myself an "Assignee" to issues/PRs as a means of organizing my personal "to-do" list but also a means of communicating to others that I've put myself on the hook to getting this done. I would like to encourage others to do the same so we know who to check in with on the current status or to restart activity on issues that have gone dormant.

[mikofski]

I think we could wrap up #823, but it is pending reviews by Cliff and Kevin. There's also the question whether to use the term "system plane" or "slope[d] plane" for the sloped plane that contains all of the trackers axes.

But I see there are 14 open issues for v0.7.2, so maybe this one can wait until v0.8.

I'll try to take a look at #516 and #517 is no one else is already working n them?

[cwhanse]

v0.8 for #823. I'm going to move #516 and #517 to v0.8 also, since they will change the API. #836 is a candidate for v0.7.2, it adds to (but doesn't otherwise change) the API.

[mikofski]

I can probably knock out #880 then

[CameronTStark]

I'm looking to shore up issues slated for 0.7.2 and to account for open issues tagged with 0.7.2. I'd like to open a discussion about where things need to go to get 0.7.2 released by Friday March 6th.

I've worked to tag issues with the 0.7.2 milestone and you can view them all here. Below are my current assessments of issues tagged as 0.7.2.

The most pressing issues due to problems that affect usability/bugs are below. There hasn't been follow up on these so I'd like to highlight them here:

• compability with pvfactors 1.4 #902 - unlikely to be complete by 0.7.2 due date. Move 0.7.2 due date or bump to 0.7.3?
• Implement another snow loss model like Bill Marion as an alt to pvwatts #577 - PR Snow coverage model from SAM #764 isfar along but stalled. @kanderso-nrel volunteered to drive. Thoughts?
• soiling_hsu doesn't work with read_tmy3 - index must be monotonic #889

These PRs are on their way to being completed by then without concern.

• access private _parse_pvgis_tmy_csv() function as read_pvgis_tmy_csv() #880 - PR from @mikofski
• Expose temperature.faiman at PVSystem and ModelChain #836 - PR from @kanderso-nrel
• add sphinx documentation build to CI #771 - PR from @CameronTStark
• soiling_hsu doesn't work with read_tmy3 - index must be monotonic #889 - PR from @mikofski

This issue appears to be closed. Can someone (maybe @cwhanse) confirm?

• Handle different time intervals in clearsky.detect_clearsky #507 - Not closed per @cwhanse below. Moved to 0.7.3

The following issues have discussions that have stalled and if they aren't started now it's unlikely to be resolved in time for the release. If there are no activity in them I plan to push them back to 0.7.3. If they require more sweeping changes they could be set for 0.8.0.

• how to organize loss functions #891 @wholmgren - Moved to 0.8.0
• use array_like instead of numeric/array-like #765 @wholmgren - Moved to 0.8.0
• Docstring for pvsystem.calcparams_xxx are inconsistent with function code #716 @cwhanse - Moved to 0.8.0

Edit: These are good general changes that have interest but need significant discussion before adoption.

There are also many issues without milestones. If there are any issues that you believe should be part of 0.7.2 please highlight them here.

I'm planning on tagging future issues/PRs with 0.7.3 unless there's an urgent bug fix or an easily completed enhancement PR.

[mikofski]

I've pushed PR #910 to address #889 the tmy3 raises ValueError for soiling_hsu issue.

[cwhanse]

#507 is not closed. The discussion wandered to other issues e.g. #506 which was closed by #596 .
I commit to closing #507 in the next release, it shouldn't change the API so could be v0.7.3

[mikofski]

FYI: @CameronTStark

• add read pvgis tmy #907 is approved and I think ready to merge
• fix read_tmy3 with year coerced not monotonic, breaks soiling #910 is waiting for approval from @wholmgren but I believe I've addressed his most recent comments, and especially if there will be a v0.7.3 release then I think it would be better to put this temporary fix in place until v0.8 - I volunteer to maintain and refactor it for v0.8

[CameronTStark]

FYI: I just updated my "accounting" comment above and am interested in any feedback.

I'm aiming to usher all 0.7.2 items through to completion ahead of creating a 0.7.2 release candidate version ahead of the final release.

[cwhanse]

That leaves #764 still to finish, it's close, I'll get it done this week.