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

Global DataGlobals: Part 1 #8331

Merged
merged 2 commits into from
Oct 8, 2020
Merged

Global DataGlobals: Part 1 #8331

merged 2 commits into from
Oct 8, 2020

Conversation

mitchute
Copy link
Collaborator

@mitchute mitchute commented Oct 5, 2020

Pull request overview

  • Begin moving DataGlobals to state
  • Noteworthy effects:
    • FluidProperties
    • InputProcessor
    • OutputProcessor
    • ScheduleManager

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
  • Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
  • Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
  • Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
  • If any diffs are expected, author must demonstrate they are justified using plots and descriptions
  • If changes fix a defect, the fix should be demonstrated in plots and descriptions
  • If any defect files are updated to a more recent version, upload new versions here or on DevSupport
  • If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
  • If structural output changes, add to output rules file and add OutputChange label
  • If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies

Reviewer

This will not be exhaustively relevant to every PR.

  • Perform a Code Review on GitHub
  • If branch is behind develop, merge develop and build locally to check for side effects of the merge
  • If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
  • If feature, test running new feature, try creative ways to break it
  • CI status: all green or justified
  • Check that performance is not impacted (CI Linux results include performance check)
  • Run Unit Test(s) locally
  • Check any new function arguments for performance impacts
  • Verify IDF naming conventions and styles, memos and notes and defaults
  • If new idf included, locally check the err file and other outputs

…luidProperties, ScheduleManager, and many others affected
@mitchute mitchute self-assigned this Oct 5, 2020
@mitchute mitchute added the Refactoring Includes code changes that don't change the functionality of the program, just perform refactoring label Oct 5, 2020
@mitchute mitchute added this to the EnergyPlus Future milestone Oct 5, 2020
@mitchute
Copy link
Collaborator Author

mitchute commented Oct 6, 2020

My Windows 10 VM isn't complaining about this. Not sure what the problem is currently.

@mitchute
Copy link
Collaborator Author

mitchute commented Oct 6, 2020

Thanks @brianlball 🤞

@Myoldmopar
Copy link
Member

There's no way to review every piece of this. It is in great shape. If it was broken -- it would be broken and CI would tell us. This will help get us a long way toward state being spread throughout the codebase. Great job!

@Myoldmopar Myoldmopar merged commit 33aabb8 into develop Oct 8, 2020
@Myoldmopar Myoldmopar deleted the global_dataGlobals_1 branch October 8, 2020 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Refactoring Includes code changes that don't change the functionality of the program, just perform refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants